Database Users

General Noob Root and ROM update Questions

So I am new to the whole Root and ROM Android arena. And I came up with a few questions that hopefully you guys can help me with.
1. I read people saying they lost their ROOT after an update from 4.1 to 4.2 or 4.2.1 to 4.2.2? How did this happen for them?
Do you have to Un-root and flash to stock before updating to a different build (Such as 4.1 to 4.2 or 4.2.1 to 4.2.2)?
2. Right now I am using a custom ROM on Android Version 4.2.2.... if a new Custom ROM with a new android version released (Let's say 4.2.3) can I flash from one Rom to the other with just wiping Cache/Factory wipe and Dalvik Cahce or is there something else I would need to do because of the Android version update?
Sorry those two questions above are very similar but I wanted to ask them both ways.
3. If I were to get bored of the Custom ROM I am currently on. Are there any Best Practices "rules" I should know about when switching from one custom ROM to another?
4. Last if I am on a custom ROM with a nightly build..... is it more common to update to every nightly build that releases? Or is it more common people to only pick and choose choice nightly build versions. And if people do update to every new Nightly build.... can you update too much and destroy your device?
Sorry guys I know these seem like very basic questions..... and Yes I did search the forums. However while I found some very basic answers nothing went into great depth in explanation. All the answers seemed to be very vague.

does anyone have some suggestions on where to find these answers?

1. If you are on stock, rooted, and you update versions of the OS, you are essentially UPDATING the /system partition. That is how you lose 'root' when upgrading. If you modify any system files while rooted, you have to either revert to stock or change those modified files back to the original before running the update.
2. Just run FACTORY RESET in your custom recovery and flash the new custom rom. No need to wipe any caches (/cache is wiped during a factory reset anyway). It doesnt matter what version to what version. Sometimes new versions might require new bootloaders, but you will be bombarded with that information here if that becomes the case.
3. See number 2. Its the same thing. backup your apps with Titanium Backup, do a Factory Reset in custom recovery and flash new rom....done.
4. doesnt matter. you can update as much or as little as you like. some people prefer stability over new shiny, but then others are just crack-flashers....and will literally flash ANYTHING posted to see what happens

Pirateghost said:
1. If you are on stock, rooted, and you update versions of the OS, you are essentially UPDATING the /system partition. That is how you lose 'root' when upgrading. If you modify any system files while rooted, you have to either revert to stock or change those modified files back to the original before running the update.
2. Just run FACTORY RESET in your custom recovery and flash the new custom rom. No need to wipe any caches (/cache is wiped during a factory reset anyway). It doesnt matter what version to what version. Sometimes new versions might require new bootloaders, but you will be bombarded with that information here if that becomes the case.
3. See number 2. Its the same thing. backup your apps with Titanium Backup, do a Factory Reset in custom recovery and flash new rom....done.
4. doesnt matter. you can update as much or as little as you like. some people prefer stability over new shiny, but then others are just crack-flashers....and will literally flash ANYTHING posted to see what happens
Click to expand...
Click to collapse
Thanks I really appreciate the response. :good: You'd be surprised how many "Tiny Parts" of answers you get from searching. Very rarely the whole answer you need.
I am glade to hear that Question 2 only requires you to just factory rest. From the misinformation gathered on other forums... I was starting to think you had to flash back to stock before updating to another Custom ROM Build.

@20mmrain
You've probably looked at a number of posts by confused newbs. For better or worse, this site is nothing like a moderated wiki, so you find treasure mixed in with trash.
Rooters fall into four broad classes:
(a) Those that "root & modify" stock ROMs
(b) Those that abandon stock and use custom ROMs and kernels
For each of the above cases, there are diligent and careful users who make full (nandroid) backups... and lazy idiots who do not. It is almost always the lazy idiots you observe coming in here in a panic, independent of whether they are in class (a) or (b).
Beyond that, newbs taking approach (a) seem to perpetually labor under the false impression that their modified versions of a stock ROM should be able to be upgraded by the OTA process - when in fact that there is absolutely no reason to believe that. The OTAs carefully check hundreds of different files before they perform any changes; if even a single one of them has been altered, the OTA aborts without making any changes.
It is *possible* that if none of those hundreds of files are changed that an OTA will succeed on a "nearly stock" ROM. When this happens though, it is quite typical that:
- the "su" binary (part of a root kit) in either /system/bin or /system/xbin gets its' setuid permissions reset by a recursive permission-setting command in the OTA
- the custom recovery can possibly be overwritten by the new stock recovery.
Folks tend to refer to either of the above as "losing root". True in principle, but they are trivially fixed up - if the user actually understands how Android rooting works. (With fastboot, you simply reflash the custom recovery, boot into that and reflash the same root kit originally used).
It's too bad that folks who put together rooting guides seem to neglect putting an emphasis on making backups. They give you both security and freedom.
Bottom line: whatever you choose to do, make nandroid backups. You don't need to keep them all on the tablet - but for convenience reasons, you should have at least one known good ROM as a backup available to be restored.
good luck

Wow that is a really in-depth explanation and that is exactly what was looking for! Since I have been working in the IT world for years I will say with pride that I am an individual who believes in safety first and always back up any important project I am working on! So I am happy to hear I made the right decision there.
I guess a great deal of my questions also stem from working in a windows based world for so long ....that I am still learning Linux/android.
Right now I do keep a nandroid backup on my nexus 7 but only one. How backups do you have? And do you just keep the rest on a thumb drive?
Sent from my Nexus 7 using xda app-developers app

20mmrain said:
Right now I do keep a nandroid backup on my nexus 7 but only one. How backups do you have? And do you just keep the rest on a thumb drive?
Click to expand...
Click to collapse
At the moment I have 6 on the tablet - all generated in the last 60 days. Two in the last two days (one a rooted stock/jdq39, another a cm10.1 nightly). Plus recent TiBu market app & data backups. 32 GB model, so I have plenty of room.
That doesn't reflect any particular strategy or goal. I hook it up to a PC every once in a while and at that time either copy off any backups worth saving or delete them. Most of the those I have on the PC will eventually be deleted as well without ever being used. You could use a USB key if you want to. Really you only need to keep one on the tablet - mostly as a convenience in case you wedge your daily driver ROM with some random mod: you can restore a working ROM right from your tablet rather than having to find a USB key or return to your PC to get the tablet booting again.
There is one type of ROM backup that I think is very useful to keep a permanent copy of - a pure stock ROM. The reason for that is that any radio images (tilapia) or bootloader upgrades that are *sometimes* delivered by OTA can be trivially installed by:
- make a backup of the current ROM
- restore a pure stock ROM backup (including the stock recovery! ***)
- take the OTA
- ***soft-boot a custom recovery and make a backup of the NEW stock ROM (including its' recovery!)
- hard-flash the custom recovery to the tablet
- restore the backup from the first step above.
Doing things this way is the safest possible way to install either a bootloader or a radio image. Not only that, but for folks that prefer to mod stock ROMs, it gives them a backup archive of /system to recover arbitrary (stock) files from.
*** soft-booting a recovery is the most convenient way to capture a stock recovery as part of a nandroid backup. I.E.
Code:
fastboot boot recoveryimagefile.img
If you hard-flash a custom recovery before you make a nandroid backup of a stock ROM, you lose the opportunity to get a copy of the stock recovery along with the rest of the stock ROM.
good luck

Moto G TELUS/Koodo rooting update!

Phone: Koodo Moto G running Motorola Android 4.3
Computer OS: WinXP sp3.
I've been reading threads/discussions for a few days now, researching before I jumped into rooting my new Moto G. Finally I chose to use the first method outlined by @paulobrien here.
This gave me root but wouldn't allow for superuser installation for properly monitoring/regulating root access. I tried multiple times with different methods and still just couldn't get superuser to install. So I tried the second recommended method.
Everything seemed to be fine as I went down the list until I followed these instructions:
Code:
Run the command 'adb-windows sideload supersu.motog.zip'. You'll notice the installation complete on your phone.
I got nothing. Repeatedly. Whether I used native ADB or his packaged version. Finally, noticing that @paulobrien had earlier stated that Motorola had messed up their recovery and that menu items weren't what they seemed, I started to experiment. Here's what I found in the recovery menu:
Code:
wipe cache partition
Actually gives you the option to install zip files from the sdcard. Duh.
Whether Motorola are really kinda inept/rushed, or if it's meant to sorta discourage people from playing with the phone's innards is anyone's guess. Whatever the reason, I copied supersu.motog.zip from my r1-motog-modifiedrecoveryroot folder - kindly supplied by @paulobrien - and boom! I have a properly installed and functioning superuser.

@ofaring Did you manage to flash CWM on Telus SW? I am unable to flash boot/recover/system that didn't come in Telus package, and I really need to. If I manage to flash CWM I can just flasch CyanogenMod and be done with it. Please help!

Flintberg said:
@ofaring Did you manage to flash CWM on Telus SW? I am unable to flash boot/recover/system that didn't come in Telus package, and I really need to. If I manage to flash CWM I can just flasch CyanogenMod and be done with it. Please help!
Click to expand...
Click to collapse
Hi Flintberg,
Yes...and no. I haven't had the time to fully investigate the current situation yet. Short answer (all I have time for right now)...I have succeeded in getting CyanogenMod, rooting, and different stock ROMs running on Android 4.3. So far, I haven't been able to properly accomplish any of that on 4.4. (Except for rooting) Trouble is, the battery indicator is wildly inaccurate with CyanogenMod installed from stock Telus Android 4.3. The trouble seems to be in the recovery image, which isn't functioning correctly in 4.4. I have to run for now. More details later.

[Q] Accelerometer/Modem Help D800

Alright, so, I'm not a huge modder, but I do like to remove the stock OS once things start slowing down (as they always do).
When I upgraded my LG G2 D800 to Cyanogenmod 11, I noticed the Accelerometer was no longer working. No big deal, I thought, it would eventually be fixed. So I just used a manual control app in the meantime.
Well, Yesterday I got a ColorCross VR headset, so I want that Accelerometer to work again. I've tried nearly everything. short of going back to stock. I think I know the solution but can't find a reliable download/get TWRP to work with my downloads. I had cm-11-20140504-SNAPSHOT-M6-d800 Installed
I found this thread http://forum.xda-developers.com/showthread.php?t=2705509 stating that a modified Kitkat Modem/baseband is needed, but the files are gone.
Then, I found this thread: http://forum.xda-developers.com/showthread.php?t=2451426 with these downloads http://downloads.codefi.re/autoprime/LG/LG_G2/G2_modems it had two modems or the LGD800, "10D_Radio" and "10O_Radio" neither worked when trying to flash the zip as downloaded using TWRP. I tried both wiping data/Cavik and flashing it right before and right after a fresh install of Cyanogenmod, both Lollipop and Kitkat versions but no luck. Couldn't open the zip file TWRP said.
So I tried a few 5.0 ROMS, CM 12 (second to latest nightly and a few others), Cloudy, Vanir, but none of them turned on my Accelerometer.
So, what I need, is an explanation on how to flash those modem files or if I was doing it correctly, a link to valid modem files. Preferably one that works with an Android 5.0.x ROM, but if I have to go back to KitKat, I can live with that, I just want my sensors to work.
Failing that, I guess I can revert all the way back to stock. But let me ask one question: Can I just flash a .zip file using TWRP if I'm not worried about making it appear completely stock (not planning on returning or selling it) without having to do the extra stuff in the guide intended for a complete return to stock? I don't need recovery to be reverted, just the original stock ROM (I tried to flash just the ROM, but either the download was damaged or I can't simply flash the stock LG G2 AT&T ROM).
I have five bucks in bitcoin I can tip whoever helps me out, either a custom ROM that installs the right modem/baseband by default and is KitKat or above or some instructions on how to get the right modem files to install + a link to them.
If a new build needs to be compiled to get the accelerometer working again, I might be able to donate a little more than that.
Right before posting this I tried downgrading to CM11-20140210-SNAPSHOT but while it installed, it still says there is no accelerometer (and doesn't auto-rotate, even when on). I also tried downgrading to CM10 (the only LG d800 CM10 on the official site) but TWRP didn't want to open the zip.
Thanks!

Neverminc, figured it out, sorry for the noob questions

Want to restore my phone to factory but afraid of bricking given circumstances

Android Version: 4.4.2
Rom: XXUGNG2-SHOstock-i-v8.1
Bootloader: I337UCUAMDL
Recovery: TWRP 2.5.0.2
I've been installing Custom ROMs for a while on this phone and the previous phones I've had (Nexus One, Galaxy Skyrocket.) My S4 hasn't had issues installing them until more developers adopted Aurora Installers and now any ROMs that use them won't work. My phone goes into a boot loop and I need to restore my previous Nandroid backup. I thought that my TWRP might be the cause, but it looks like nowadays the only way to update TWRP is through the GOO Manager. Unfortunately for whatever reason that doesn't work properly and I can't figure out how to get it in any other way. So for a while I had this older ROM installed but now that we're well into Lollipop I decided to try another ROM (GOLDENEYE|XXUHOD7 LOLLiPOP TW|5.1.15), but again it had Aurora and failed, and this time it looks like it messed up my bootloader because now I have the unlock icon whenever I turn on my phone (I don't care much about that because my phone is well outside of warranty at this point, but I'd prefer it be removed)
So I was considering just using ODIN to revert all the way back and starting from scratch, but it looks like my phone will be bricked. So basically I'm at a standstill because I obviously don't want to brick my phone, but at the same time I'm not satisfied with my current ROM since it's quite long in the tooth and isn't even Lollipop based. Any help/suggestions would be greatly appreciated.
TIA

One thing you might try here, and another here.

dvandam said:
Android Version: 4.4.2
Rom: XXUGNG2-SHOstock-i-v8.1
Bootloader: I337UCUAMDL
Recovery: TWRP 2.5.0.2
I've been installing Custom ROMs for a while on this phone and the previous phones I've had (Nexus One, Galaxy Skyrocket.) My S4 hasn't had issues installing them until more developers adopted Aurora Installers and now any ROMs that use them won't work. My phone goes into a boot loop and I need to restore my previous Nandroid backup. I thought that my TWRP might be the cause, but it looks like nowadays the only way to update TWRP is through the GOO Manager. Unfortunately for whatever reason that doesn't work properly and I can't figure out how to get it in any other way. So for a while I had this older ROM installed but now that we're well into Lollipop I decided to try another ROM (GOLDENEYE|XXUHOD7 LOLLiPOP TW|5.1.15), but again it had Aurora and failed, and this time it looks like it messed up my bootloader because now I have the unlock icon whenever I turn on my phone (I don't care much about that because my phone is well outside of warranty at this point, but I'd prefer it be removed)
So I was considering just using ODIN to revert all the way back and starting from scratch, but it looks like my phone will be bricked. So basically I'm at a standstill because I obviously don't want to brick my phone, but at the same time I'm not satisfied with my current ROM since it's quite long in the tooth and isn't even Lollipop based. Any help/suggestions would be greatly appreciated.
TIA
Click to expand...
Click to collapse
There are flashable zips of TWRP floating around to update and the TWRP thread in our section says to use the TWRP Manager app on the Play Store. As far as using ODIN, you won't be bricked. The unlock icon shows up when it detects the system files aren't stock/root is in place. Your bootloader should still be in tact, and if you can still boot into recovery that confirms it. Either way, you just need to use a different method to update TWRP and you should be fine.

Well I feel like a f-ing nimrod..
I failed to mention in my description that when I first tried to install, not only did I get the Unlock icon, but I got the "Software not authorized by AT&T..." error message that prevented me from doing anything. However, I thought this was related to my phone being carrier locked. I found out later that my phone was unlocked a while ago so that wasn't it. Had I looked more closely at the error I would have seen that it was a Kernel error. Turns out I had to install a LOKI'd Kernel. Not exactly sure why, but that was the only one that worked. Now the new ROM is installed and I'm restoring my apps now.
If nothing else, I got my TWRP updated finally, so I like to think this wasn't all for naught. Thanks for the insight anyways. This was easier than doing an ODIN back and forth.

This is because you're on the MDL bootloader. You need to search the forums for your phone in regard to the MDL bootloader and loki'd ROMs. When you see the "software not authorized. .." message, it just means you need to flash a loki'd kernel for your device. Search for Jeeboo's Recovery and Kernel and you should be right a rain. Good luck.
Edit: I was half awake when I tried to answer your question, and somehow missed that you had discovered the loki'd kernel already. The reason for this is because the MDL bootloader is susceptible to the loki exploit, which for all intents and purposes is the equivalent of unlocking the bootloader. I've been using Jeeboo's recovery for a year or so and never had an issue with any ROM I tried. The kernel cones in handy for those that need a loki'd kernel. There's a ton of easy to find info in the forums to help you get a better understanding of the MDL and how loki applies to it.

Couple of post rooting/flashing questions and assumptions

Yesterday I bit the bullet, rooted and flashed my N9005 with CWM and Temasek's CM12.1 rom.. and wow, wished Id done this sooner..
Device is now so clean and slick, and I just need to hunt down and find the apps I want to put on. I did think I may lose some functionality, but I wasn't a heavy user of some of the Note's features, so wasn't too worried, and since I found Spen Command, the stylus is now better than before!
The process was very easy, and the guides I used were very good.. however, I seemed to have some screens that weren't referred to or documented, and although everything seems to be working.. I just had a few question...
After I used ODIN to install CWM Recovery, the phone booted, however, the guide implied the device should fully reboot to then copy SuperSU... but I was prompted with a recovery menu asking if I wanted to root the phone, so I said yes.. then rebooted to copy the SuperSU over, reboot into recovery and install the zip, rebooted and confirmed root.
Nothing I had read had mentioned about the first menu asking if I wanted to root, and I thought the rooting process was the installation of SuperSU?
I then flash the ROM and Gapps... few issues at first, but after applying the Rom OTA update, all is well! SuperSU is gone, but I assume that being a Custom Rom it is essentially already rooted so doesn't need it.
I installed CW Rom Manager but this actually told me the latest version of recovery was actually older than the one I had installed, and that my devices wasn't actually supported... Also, much of the content available through it seem out of date, so I removed it.
Think ill stick with this ROM anyway and await the Offical Note3 CM12.1.. although not really seeing much info about it, so don't even know if it will!

DocSoton said:
Yesterday I bit the bullet, rooted and flashed my N9005 with CWM and Temasek's CM12.1 rom.. and wow, wished Id done this sooner..
Device is now so clean and slick, and I just need to hunt down and find the apps I want to put on. I did think I may lose some functionality, but I wasn't a heavy user of some of the Note's features, so wasn't too worried, and since I found Spen Command, the stylus is now better than before!
The process was very easy, and the guides I used were very good.. however, I seemed to have some screens that weren't referred to or documented, and although everything seems to be working.. I just had a few question...
After I used ODIN to install CWM Recovery, the phone booted, however, the guide implied the device should fully reboot to then copy SuperSU... but I was prompted with a recovery menu asking if I wanted to root the phone, so I said yes.. then rebooted to copy the SuperSU over, reboot into recovery and install the zip, rebooted and confirmed root.
Nothing I had read had mentioned about the first menu asking if I wanted to root, and I thought the rooting process was the installation of SuperSU?
I then flash the ROM and Gapps... few issues at first, but after applying the Rom OTA update, all is well! SuperSU is gone, but I assume that being a Custom Rom it is essentially already rooted so doesn't need it.
I installed CW Rom Manager but this actually told me the latest version of recovery was actually older than the one I had installed, and that my devices wasn't actually supported... Also, much of the content available through it seem out of date, so I removed it.
Think ill stick with this ROM anyway and await the Offical Note3 CM12.1.. although not really seeing much info about it, so don't even know if it will!
Click to expand...
Click to collapse
Seriously dude. Go to temaseks thread and care to read at least first two posts. Please do it for all roms. Because if you did you would know that :
TWRP is RECOMMENDED.
To get root access you have to flash SUPERSU in RECOVERY. In that rom at least.
Unbelievable