Develop Bugs

★[Guide]Beginners/noob,Android modding:Where to start★

!!!!☆■PLEASE PRESS THANKS INSTEAD OF SAYING IT IM SO SICK OF PEOPLE SAYING THANKS WHEN IN THE RULES IT SAYS TO USE THE THANKS BUTTON□★!!!!!!!
This is a beginners guide to start modifying your Android device. When I joined the website I felt like I didn't know where to start. So I thought I could make this thread to get people started.
*I will not be held responsible for any damage that may be caused to your device.
First things first your going to need to root your device. What rooting does is it allows special access to things in your phone. Without root custom roms and custom recoveries will not work. Also some apps require root to work. So to root your device search for the name of your device in the search box. Once you find your device then go to the Android development section. And usually near the top there will be a guide on how to root your device.
If your can't find or your device doesn't have a forum section (for example the Us Cellular Galaxy s4) then search for a similar device. So I have the Us cellular galaxy s4 and it doesn't have a forum section. So I could look at the Verizon or At&T galaxy s4 section and see if the root method with work on my us cellular galaxy s4. Thankfully there is a method that works for the us cellular version too. If you still can't find a root method for your device then I would Google it and see what you can find.
Once you have gotten root access then the next step is to install a custom recovery.
IF U WANT TO CHECK IF YOU HAVE SUCCESSFULLY GOTTEN ROOT ACCESS THEN DOWNLOAD THE ROOT CHECKER APP.
Ok so what a custom recovery is basically a tool to install/ flash things to your device. For example If I want a transparent status bar then I can download an s4 transparent status bar. Then I can go into recovery mode. After that since I have a custom recovery I can install the new status bar in recovery mode. Then reboot my phone. And boom I have a transparent status bar. Be sure to check out the link. It will further Explain custom recoveries.
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
Ok so to get a custom recovery you can follow the link above or your can do the same thing u did for root. Search your device. Then go to the Android development section and look for a thread on how to install a custom recovery. There are different types/versions of recoveries. Clock work mod recovery is one of the more popular ones and is what I personally use and I recommend. TWRP (team win recovery project is another one and is good too.)
After you get a custom recovery installed you need to make a backup. In case something goes wrong by user error or accident you can fix your device.
A back up is needed because if I would try to install a rom and for some reason it doesnt boot up then your going to need to return to what you were previously on. For example I have my galaxy s4 and If i make a backup right before I install a new rom. Then I try installing a rom and for whatever reason it doesn't work. I can go back into recovery mode and I can install my back up. And the backup will be everything that I had on my device before I tried to install a new rom. Once you have a backup then go to the next step.
Now the best part custom roms. Ok a custom rom is kinda hard to explain but im gonna try to. So a rom is basically firmware. And u can have different types of roms (firmware) for your device. **THE NUMBER ONE RULE IS TO NEVER INSTALL A ROM THAT IS NOT MEANT FOR YOUR PHONE. THIS IS 99 PERCENT OF WHY PEOPLE HARD BRICK THEIR DEVICE. **
So generally there are too different versions of roms. Stock based roms and aosp/ cyanogen based roms. Stock roms have generally the same look but may offer more options and settings for things. Some stock based roms have options to Change the look too.
Aosp(cyanogen mod,pac man, carbon) roms are going to change the look a lot. And have more options to Change Things too. Check out cyanogenmod.com to see what I mean.
Roms are a lot of fun to expirment with and see which ones you like best.
So your ready to get a custom rom.
Make sure you have a back up before you continue.
1. Dowload a rom to your device.
A good rom to try is cyanogen mod. It's an aosp based rom. Follow this link and see if your device is compatible.
get.cm/
REMEMBER U MUST DOWNLOAD A ROM THAT IS MEANT FOR YOUR DEVICE ONLY!!!!!
2. If you are going to install cyanogen mod or any aosp you are also going to need g apps. What g apps is is a package of apps. Basically of all the stock apps. Stock roms have it built in.
You can get get g apps from here
http://goo.im/gapps
If you want to check out other roms then go to your device in the forums then go to the Android development section. And look around there should be plenty to choose from.
3. So if you are installing cyanogen mod make sure you have gapps if you are installing a stock based rom you don't need it.
4.Boot into recovery mode. You can download rom manager from the play store and go into the app and press boot into recovery mode or do it manually by using the hard keys. Google it if you can't get into recovery mode.
5.Once in recovery mode if u are installing cyanogen mod do a wipe data/factory reset.
If you are installing a stock based rom skip that step unless you want to wipe data. Or if where you found the rom it says to wipe data.
6.flash the rom you installed. Remember where you put it when you downloaded it.
7. If you needed it find gapps then flash(install) that.
If you didn't need gapps then skip that step.
8. Wipe the cache partion
9. Wipe the davilk cache. *Its under advanced* This is important so you don't get a boot loop.
10. Reboot system
11. Enjoy your new rom.
Common errors:
If you get stuck at the boot logo you probably forgot to wipe the davilk cache. Its under advanced options in recovery.
If you try to install cyanogen mod and get an error saying system has stopped and that error keeps showing up then you used the wrong gapps package. Dowload the one closest to the top of the page if u are trying to download cyano
If u have any questions at all about anything feel free to ask them on this thread. Or in the q and a section. Or pm me.
☆■PLEASE PRESS THANKS INSTEAD OF SAYING IT IM SO SICK OF PEOPLE SAYING THANKS WHEN IN THE RULES IT SAYS TO USE THE THANKS BUTTON□★
Have a nice day!

Very Useful guide for beginners good work!!!

AndreRaptor said:
Very Useful guide for beginners good work!!!
Click to expand...
Click to collapse
I appreciate the kind words.
-If I've helped press thanks. Don't say it.-
Sent from my SCH-R970 using Tapatalk 2

very imformative. i will point others to this

how to remove boot menu manager and also remove custom rom installed
how to remove boot menu manager and also remove custom rom installed.
I m using motorola atrix 2 .. i have in system 1 stock rom, i was trying with custom roms . i want to delete all other roms and boot menu manager.... please help....

Very nicely put together....
Pressed Thanks!

mrblink said:
Thanks for the tips
Click to expand...
Click to collapse
Read the bottom of the post....
Sent from my SCH-R970 using Tapatalk 4

Do I need to do some backup before Rooting too?
Hi,
First of all, I really appreciate your work for helping Noobs like me, for teaching all these things...
I was going to do perform experiments on my Android phone, and I would like to be sure regarding the steps. Of course, nobody wants to go wrong while doing this.
So, Do I need to do any sort of Backup before Rooting process, too?
Or it is just simple like:
Root your Phone
Install some Custom Recovery
Flash some cool Custom ROMs (optional)
Also, Is there anything, that I should be aware of, regarding Bootloaders? People discuss so much about Locked/Unlocked bootloaders.
I checked the Hidden Menu of my phone and it says that my Bootloader is Locked.
It would be appreciating, if you can add something regarding this Bootloader thing in your Post too.
Thanks a lot for this Guide :good:

Great to see xda cares about the noobs. Ive down my share of flashing roms and mods but always good to learn more.
Sent from my Nexus 4 using xda app-developers app

Clean
Clean and to the point. Looking to get into more of the coding and building your own ROM where might be a solid software to buy etc. Thanks

no keyboard
Hello… I will be bookmarking the thread for educating my NOOB brain. I have had an ongoing challenge with not having a keyboard after flashing different ROM's and cannot enter anything. What am I doing incorrectly?

scottpub said:
Hello… I will be bookmarking the thread for educating my NOOB brain. I have had an ongoing challenge with not having a keyboard after flashing different ROM's and cannot enter anything. What am I doing incorrectly?
Click to expand...
Click to collapse
The G Apps you downloaded didn't work.... flash your backup to fix this, of course you will be back to normal and still have root. Find another ROM or find a better G Apps. The keyboard not working happened to my nexus 4 after flashing cyanogen... oh well. NEXT!!!!

A helpful tool would be the clockwork mod ROM manager that you can download from either the Play store or the Amazon app market. You can download the gapps zip directly from the app as well as boot into recovery from the app so you can install the zip. I would also recommend buying the pro (it's 99 cents and you are supporting a great team of devs) app so you can update your CM ROM and switch ROMs if you like doing that.
Sent from my LG-D950 using xda app-developers app
---------- Post added at 02:21 PM ---------- Previous post was at 02:15 PM ----------
Clockwork Mod also has a touch recovery that is really nice to have to navigate though. You can buy it on the app or you can download it off their site for free. I use it on all of my devices and swear by it. There aren't very many that aren't supported from the major manufacturers so it's a great tool to have in your arsenal. That and it makes installing zips easier for those newer to the wonderful world of Android.
Sent from my LG-D950 using xda app-developers app

thanks..help me alot

noob razr maxx with newest kk update
hi i am new can i root my phone and make the tether avaliable on my moto razr maxx hd ? it has newest update

Nice guide really helped

new here couldn't post in development forum
I just want to give a big thanks to "mohammad.afaneh" ! I just installed Superliterom V5.0 on my
verizon galaxy S3, with no troubles. It's running smooth and looks great.
Simple enough just had to follow your directions, which were perfect..
Thank you also to everyone that makes this site the bible of everything Android... period..
Thanks Again
Mo's Derf

Rooted and
Yes, I rooted my phone and did all the things I Google searched. The the phone (Sprint Galaxy S6 SM-G920P) worked fine. I did the Renegade ROM and I got stuck on the Load screen for Renegade. When it didn't work I accidentally wiped my entire phone and tried saving it with Cm-13.0-201xxxxxx, but it sucks. It will not let me do anything. I am searching for a ROM I can flash with TWRP that will allow me to get my phone up and working properly. Can any of you help

How to do the samething when the touchscreen is not working properly
I got the stock rom for my device and the touchscreen does not work properly after flashing it to my device, surely I did something wrong or the rom from the manufacturer is not working.
I have seen newer and differnt versions I can use for the THL 5000 mkt or MK 6592 chipset, just all the ROMs want a person to have some android interface where the android touchscreen is working fine. So my thought is how do I go about either finding another custom rom which will work with this device when most if not all use android touchscreens for the smart phones and I can't find roms with scatter files and bin files for this model.
Touchscreen works in a weird way where pressing the lower screen selects things above it.
​
noahthedominator said:
!!!!☆■PLEASE PRESS THANKS INSTEAD OF SAYING IT IM SO SICK OF PEOPLE SAYING THANKS WHEN IN THE RULES IT SAYS TO USE THE THANKS BUTTON□★!!!!!!!
This is a beginners guide to start modifying your Android device. When I joined the website I felt like I didn't know where to start. So I thought I could make this thread to get people started.
*I will not be held responsible for any damage that may be caused to your device.
First things first your going to need to root your device. What rooting does is it allows special access to things in your phone. Without root custom roms and custom recoveries will not work. Also some apps require root to work. So to root your device search for the name of your device in the search box. Once you find your device then go to the Android development section. And usually near the top there will be a guide on how to root your device.
If your can't find or your device doesn't have a forum section (for example the Us Cellular Galaxy s4) then search for a similar device. So I have the Us cellular galaxy s4 and it doesn't have a forum section. So I could look at the Verizon or At&T galaxy s4 section and see if the root method with work on my us cellular galaxy s4. Thankfully there is a method that works for the us cellular version too. If you still can't find a root method for your device then I would Google it and see what you can find.
Once you have gotten root access then the next step is to install a custom recovery.
IF U WANT TO CHECK IF YOU HAVE SUCCESSFULLY GOTTEN ROOT ACCESS THEN DOWNLOAD THE ROOT CHECKER APP.
Ok so what a custom recovery is basically a tool to install/ flash things to your device. For example If I want a transparent status bar then I can download an s4 transparent status bar. Then I can go into recovery mode. After that since I have a custom recovery I can install the new status bar in recovery mode. Then reboot my phone. And boom I have a transparent status bar. Be sure to check out the link. It will further Explain custom recoveries.
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
Ok so to get a custom recovery you can follow the link above or your can do the same thing u did for root. Search your device. Then go to the Android development section and look for a thread on how to install a custom recovery. There are different types/versions of recoveries. Clock work mod recovery is one of the more popular ones and is what I personally use and I recommend. TWRP (team win recovery project is another one and is good too.)
After you get a custom recovery installed you need to make a backup. In case something goes wrong by user error or accident you can fix your device.
A back up is needed because if I would try to install a rom and for some reason it doesnt boot up then your going to need to return to what you were previously on. For example I have my galaxy s4 and If i make a backup right before I install a new rom. Then I try installing a rom and for whatever reason it doesn't work. I can go back into recovery mode and I can install my back up. And the backup will be everything that I had on my device before I tried to install a new rom. Once you have a backup then go to the next step.
Now the best part custom roms. Ok a custom rom is kinda hard to explain but im gonna try to. So a rom is basically firmware. And u can have different types of roms (firmware) for your device. **THE NUMBER ONE RULE IS TO NEVER INSTALL A ROM THAT IS NOT MEANT FOR YOUR PHONE. THIS IS 99 PERCENT OF WHY PEOPLE HARD BRICK THEIR DEVICE. **
So generally there are too different versions of roms. Stock based roms and aosp/ cyanogen based roms. Stock roms have generally the same look but may offer more options and settings for things. Some stock based roms have options to Change the look too.
Aosp(cyanogen mod,pac man, carbon) roms are going to change the look a lot. And have more options to Change Things too. Check out cyanogenmod.com to see what I mean.
Roms are a lot of fun to expirment with and see which ones you like best.
So your ready to get a custom rom.
Make sure you have a back up before you continue.
1. Dowload a rom to your device.
A good rom to try is cyanogen mod. It's an aosp based rom. Follow this link and see if your device is compatible.
get.cm/
REMEMBER U MUST DOWNLOAD A ROM THAT IS MEANT FOR YOUR DEVICE ONLY!!!!!
2. If you are going to install cyanogen mod or any aosp you are also going to need g apps. What g apps is is a package of apps. Basically of all the stock apps. Stock roms have it built in.
You can get get g apps from here
http://goo.im/gapps
If you want to check out other roms then go to your device in the forums then go to the Android development section. And look around there should be plenty to choose from.
3. So if you are installing cyanogen mod make sure you have gapps if you are installing a stock based rom you don't need it.
4.Boot into recovery mode. You can download rom manager from the play store and go into the app and press boot into recovery mode or do it manually by using the hard keys. Google it if you can't get into recovery mode.
5.Once in recovery mode if u are installing cyanogen mod do a wipe data/factory reset.
If you are installing a stock based rom skip that step unless you want to wipe data. Or if where you found the rom it says to wipe data.
6.flash the rom you installed. Remember where you put it when you downloaded it.
7. If you needed it find gapps then flash(install) that.
If you didn't need gapps then skip that step.
8. Wipe the cache partion
9. Wipe the davilk cache. *Its under advanced* This is important so you don't get a boot loop.
10. Reboot system
11. Enjoy your new rom.
Common errors:
If you get stuck at the boot logo you probably forgot to wipe the davilk cache. Its under advanced options in recovery.
If you try to install cyanogen mod and get an error saying system has stopped and that error keeps showing up then you used the wrong gapps package. Dowload the one closest to the top of the page if u are trying to download cyano
If u have any questions at all about anything feel free to ask them on this thread. Or in the q and a section. Or pm me.
☆■PLEASE PRESS THANKS INSTEAD OF SAYING IT IM SO SICK OF PEOPLE SAYING THANKS WHEN IN THE RULES IT SAYS TO USE THE THANKS BUTTON□★
Have a nice day!
Click to expand...
Click to collapse

Am I the only one with these bugs?

Hi,
I'm new here so please go easy on this "noob"
It was my first to unlock and root my phone, followed by flashing a stock ROM (Which is exactly why I rooted it)
I flashed this JB 4.2.2 stock build [ROM] [OTA][GSM] Android 4.2.2 JDQ39: Rooted | Galaxy Nexus > XDA for my Galaxy Nexus
Now...
I can't disable Next-word suggestions in the Language & Input -> Google Keyboard Settings
Also, I noticed a few seconds of lag when pressing the power button to unlock the phone, when viewing recent apps (via the soft-key), and when opening the Camera too
Also, when I choose the "Recent Apps" soft key.. it's as the app that's currently being used is minimised and the homescreen is shown without any icons
The Build came with Busybox pre-installed and now its gone after a day of using my phone... I literally can't find it.
I searched in the play store "BusyBox" and the result is 3 different apps with the same name!
Any Advice?

AMKhatri said:
Hi,
I'm new here so please go easy on this "noob"
It was my first to unlock and root my phone, followed by flashing a stock ROM (Which is exactly why I rooted it)
I flashed this JB 4.2.2 stock build [ROM] [OTA][GSM] Android 4.2.2 JDQ39: Rooted | Galaxy Nexus > XDA for my Galaxy Nexus
Now...
I can't disable Next-word suggestions in the Language & Input -> Google Keyboard Settings
Also, I noticed a few seconds of lag when pressing the power button to unlock the phone, when viewing recent apps (via the soft-key), and when opening the Camera too
Also, when I choose the "Recent Apps" soft key.. it's as the app that's currently being used is minimised and the homescreen is shown without any icons
The Build came with Busybox pre-installed and now its gone after a day of using my phone... I literally can't find it.
I searched in the play store "BusyBox" and the result is 3 different apps with the same name!
Any Advice?
Click to expand...
Click to collapse
go back to recovery, format/wipe /system partition, reflash rom.
For your reference, a good app to install bb is stephen (stericsson)'s busybox installer (play store link). Obviously, it needs root.
Next time, read the stickies.
http://forum.xda-developers.com/showthread.php?t=1812959
How do I get “root”?
If you are booted into a custom recovery (recoveries will be covered later), root is enabled by default. If you want root while booted into Android, you will need to place two files on your system partition: an “su” binary which grants root access, and a superuser app that manages that access. The two that are available are ChainsDD’s Superuser and Chainfire’s SuperSU. Usually these files are packaged up in a zip file that is flashable using a custom recovery, but they can be flashed manually using ADB. Both of these methods will be described below.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=26328017&postcount=123
As you probably noticed by now, you didn't need to flash a full "custom stock ROM" to root.

beekay201 said:
go back to recovery, format/wipe /system partition, reflash rom.
For your reference, a good app to install bb is stephen (stericsson)'s busybox installer (play store link). Obviously, it needs root.
Next time, read the stickies.
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showpost.php?p=26328017&postcount=123
As you probably noticed by now, you didn't need to flash a full "custom stock ROM" to root.
Click to expand...
Click to collapse
Thanks for replying!
I'm totally new to this rooting &/ flashing thing, so please go easy
So, what you're saying is that I should boot into fastboot mode, wipe system partition (this will format the whole SD card right?), install the same ROM again?
I guess I'll need to install Titanium Backup to backup my apps and settings, I'll have to search for an article for the best way to do it as well..
Can I do it like this:
Open "Rom Manager", Select "Install ROM from SD Card", install it.. ???
PS: Do you have a recommendation for a better ROM, perhaps my choice of ROM wasn't correct...

AMKhatri said:
Thanks for replying!
I'm totally new to this rooting &/ flashing thing, so please go easy
So, what you're saying is that I should boot into fastboot mode, wipe system partition (this will format the whole SD card right?), install the same ROM again?
I guess I'll need to install Titanium Backup to backup my apps and settings, I'll have to search for an article for the best way to do it as well..
Can I do it like this:
Open "Rom Manager", Select "Install ROM from SD Card", install it.. ???
PSo you have a recommendation for a better ROM, perhaps my choice of ROM wasn't correct...
Click to expand...
Click to collapse
You can wipe the system partition in a custom recovery (dont know if you can with stock). And yes you could flash via ROM manager but I wouldnt recommend it. I am on XenonHD 11.1 and loving it. But roms are a personal choice so there is no 'best' ROM. Just try out.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
You can wipe the system partition in a custom recovery (dont know if you can with stock). And yes you could flash via ROM manager but I wouldnt recommend it. I am on XenonHD 11.1 and loving it. But roms are a personal choice so there is no 'best' ROM. Just try out.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
The tutorial I followed didn't mention using the ROM manager, but I had not choice.. becuase whenever I went into fastboot mode manually, it got stuck on the screen displaying Google (I waited for minutes without any luck)
How would you recommend CyanogenMod 10.1.2 against the stock 4.2.2 which I have currently?
I read these threads as well whereby they said that there is no "real" solution to the issues:
http://forum.xda-developers.com/showthread.php?t=2178962
http://forum.xda-developers.com/showthread.php?t=2363872

AMKhatri said:
Thanks for replying!
I'm totally new to this rooting &/ flashing thing, so please go easy
So, what you're saying is that I should boot into fastboot mode, wipe system partition (this will format the whole SD card right?), install the same ROM again?
I guess I'll need to install Titanium Backup to backup my apps and settings, I'll have to search for an article for the best way to do it as well..
Can I do it like this:
Open "Rom Manager", Select "Install ROM from SD Card", install it.. ???
PS: Do you have a recommendation for a better ROM, perhaps my choice of ROM wasn't correct...
Click to expand...
Click to collapse
Mr., please, read the LINK i gave you! THIS ONE ->>>> http://forum.xda-developers.com/showthread.php?t=1812959
If you read it, you'll stop thinking you need to be doing anything at this point in FASTBOOT interface! Like mrgnex says, you need to be on a custom recovery to format /system. (Have you read the link yet? By now you should know that the /system partition and the /sdcard/ (aka userdata) are 2 different things!)
mrgnex said:
You can wipe the system partition in a custom recovery (dont know if you can with stock). (...) roms are a personal choice so there is no 'best' ROM. Just try out.
Click to expand...
Click to collapse
+1
For your reference, you can't erase /system in stock recovery.
AMKhatri said:
The tutorial I followed didn't mention using the ROM manager, but I had not choice.. becuase whenever I went into fastboot mode manually, it got stuck on the screen displaying Google (I waited for minutes without any luck)
How would you recommend CyanogenMod 10.1.2 against the stock 4.2.2 which I have currently?
I read these threads as well whereby they said that there is no "real" solution to the issues:
http://forum.xda-developers.com/showthread.php?t=2178962
http://forum.xda-developers.com/showthread.php?t=2363872
Click to expand...
Click to collapse
Stop! THERE'S NO NEED FOR FASTBOOT HERE!

Thanks Guys for replying.
Yes, I read the info in the link, it was very helpful.
I'm still confused though.. "Fast boot" and "Recovery" are they the same thing?
I tried a "fix" mentioned by someone about using a live wallpaper such as "Water", I tried it and it's been 1/2 hour and it's really smooth compared to before...
Yes, I do have a custom recovery, actually I don't know why, but It seems I've got two according to ROM Manager.
It says I've got Clockwork Mod Recovery & TWRP.
I also tried going into recovery (Volume up + Down + Power) and it worked this time, when I select recovery, it goes into CWRM
I also did a bit of research about CyanogenMod 10.1.2 and from what I could gather it's liked by people a lot.
I'm guessing that definitely some time ahead it'll get all "laggy" again, Is there any reason according to you why I shouldn't install it compared to the stock 4.2.2 I have?

AMKhatri said:
Thanks Guys for replying.
Yes, I read the info in the link, it was very helpful.
I'm still confused though.. "Fast boot" and "Recovery" are they the same thing?
I tried a "fix" mentioned by someone about using a live wallpaper such as "Water", I tried it and it's been 1/2 hour and it's really smooth compared to before...
Yes, I do have a custom recovery, actually I don't know why, but It seems I've got two according to ROM Manager.
It says I've got Clockwork Mod Recovery & TWRP.
I also tried going into recovery (Volume up + Down + Power) and it worked this time, when I select recovery, it goes into CWRM
I also did a bit of research about CyanogenMod 10.1.2 and from what I could gather it's liked by people a lot.
I'm guessing that definitely some time ahead it'll get all "laggy" again, Is there any reason according to you why I shouldn't install it compared to the stock 4.2.2 I have?
Click to expand...
Click to collapse
So to get things clear:
No fastboot and recovery arent the same thing.
Vol up+down+power brings you into fast boot and not recovery.
Apparently you dont have 2 custom recoverys since you booted into cwm.
Cm10 is great. But there are many great roms out there. You can start off with cm and then (if you please) look further.
I dont see any reason to not install cm10.1.2 since a whole team built and optimized it. So basically it is a better stock.
When you think your phone is slow you should look into the custom kernels. Thats a different story which I will not begin before you want to
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
So to get things clear:
No fastboot and recovery arent the same thing.
Vol up+down+power brings you into fast boot and not recovery.
Apparently you dont have 2 custom recoverys since you booted into cwm.
Cm10 is great. But there are many great roms out there. You can start off with cm and then (if you please) look further.
I dont see any reason to not install cm10.1.2 since a whole team built and optimized it. So basically it is a better stock.
When you think your phone is slow you should look into the custom kernels. Thats a different story which I will not begin before you want to
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! Now it's definitely clear!
I'll download CM10.1.2 tomorrow and will decide to install it once Stock JB 4.2.2 starts acting up again.
In the meantime I'll read on about kernels, please keep don't close this thread...yet.

clerk usdEuro
I've decided that I will test out the Rom that I have currently (4.2.2) for a few weeks, and then flash CM.
I wanted to know one more thing, Is it bad to flash ROMs to your phone every now and then?
Because I've seen people flashing different ROMs on their phone, I don't wanna damage my phone as I want it to last as long as I can make it.
(by "Bad" I mean... does it reduce the phone's life or it's hardware's life span)

AMKhatri said:
I've decided that I will test out the Rom that I have currently (4.2.2) for a few weeks, and then flash CM.
I wanted to know one more thing, Is it bad to flash ROMs to your phone every now and then?
Because I've seen people flashing different ROMs on their phone, I don't wanna damage my phone as I want it to last as long as I can make it.
(by "Bad" I mean... does it reduce the phone's life or it's hardware's life span)
Click to expand...
Click to collapse
No it can't. I was a flashaholic (until I discovered XenonHD) and my phone didn't got worse. Only overclocking the CPU and gpu can affect the life of the CPU or gpu (or both XD). Just do a fresh install everytime and read the post of the ROM of your choice to see what to do to get it working optimally. If you have any problems just ask.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
No it can't. I was a flashaholic (until I discovered XenonHD) and my phone didn't got worse. Only overclocking the CPU and gpu can affect the life of the CPU or gpu (or both XD). Just do a fresh install everytime and read the post of the ROM of your choice to see what to do to get it working optimally. If you have any problems just ask.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thanks...
I'll flash CM in a week or two, as I'm on a tight schedule currently, and I also wanna note down the average battery time I get out of 4.2.2

So... since 4.3 is now out, I was thinking it'd be better for me to flash it other than anything else.
I'll most probably download the stock rom from:
https://developers.google.com/android/nexus/images#yakjujwr66v
So far I came across this thread having the steps to flash 4.3
http://forum.xda-developers.com/showthread.php?t=2377307
But I wanna flash it and lose my data, so that it's as fresh as it can be...
Will that work if I use "wugfresh root toolkit"?

AMKhatri said:
So... since 4.3 is now out, I was thinking it'd be better for me to flash it other than anything else.
I'll most probably download the stock rom from:
https://developers.google.com/android/nexus/images#yakjujwr66v
So far I came across this thread having the steps to flash 4.3
http://forum.xda-developers.com/showthread.php?t=2377307
But I wanna flash it and lose my data, so that it's as fresh as it can be...
Will that work if I use "wugfresh root toolkit"?
Click to expand...
Click to collapse
With the stock package there is no need for a toolkit.
Hell, there's no reason for a toolkit any time.
Sent from my Galaxy Nexus

Pirateghost said:
With the stock package there is no need for a toolkit.
Hell, there's no reason for a toolkit any time.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
What was I thinking...
I apologize guys... I guess I wasn't thinking straight as its past midnight here...
So just to clarify stuff so that I don't end up doing something wrong:
-> Head into Recovery Mode (with usb debugging enabled... connect usb cable to phone and pc)
-> Wipe System
-> Wipe Cache
-> Install from SD card (select .zip file)
right?
Also, I performed a backup of the applications I have via Titanium Backup, They'll work on 4.3 when I restore them right? or do you recommend downloading them from the play store again?
Sorry for being such a noob, and Thanks for your responses!

backup everything from your /sdcard to your computer, titanium backups and a nandroid
the google stock package is NOT flashable in CWM/TWRP
if you follow the GOOGLE instructions it WILL wipe your device (remember that backup you made of everything?)
alternatively you can make sure and have adb/fastboot working on your computer properly, extract all the files out of the zip (including the tar.gz located inside), and in recovery, do a factory reset, then boot to fastboot, fastboot flash system and boot ....
as for Titanium Backup, there is a work around to get it working on 4.3, but root is lacking full power.

Pirateghost said:
backup everything from your /sdcard to your computer, titanium backups and a nandroid
the google stock package is NOT flashable in CWM/TWRP
if you follow the GOOGLE instructions it WILL wipe your device (remember that backup you made of everything?)
alternatively you can make sure and have adb/fastboot working on your computer properly, extract all the files out of the zip (including the tar.gz located inside), and in recovery, do a factory reset, then boot to fastboot, fastboot flash system and boot ....
as for Titanium Backup, there is a work around to get it working on 4.3, but root is lacking full power.
Click to expand...
Click to collapse
Thanks!
I'm now on Android 4.3
I'm full of excitement atm :victory:
I took a backup of my apps using titanium backup, I installed it but can't use it, it says I need root (which I already had before).
I read online somewhere that I need to root again, but I don't wanna lose all my data/ apps I installed again...
Any ideas?
If I use Wugfresh Nexus Root Toolkit... will I lose my data?
Thanks for the continued support!

AMKhatri said:
Thanks!
I'm now on Android 4.3
I'm full of excitement atm :victory:
I took a backup of my apps using titanium backup, I installed it but can't use it, it says I need root (which I already had before).
I read online somewhere that I need to root again, but I don't wanna lose all my data/ apps I installed again...
Any ideas?
If I use Wugfresh Nexus Root Toolkit... will I lose my data?
Thanks for the continued support!
Click to expand...
Click to collapse
Seriously, how hard can it be for you people to waste 5, 5!!! minutes to browse the forums.
http://forum.xda-developers.com/showthread.php?t=2377318

Thanks!
According to a friend's recommendation I used Wugfresh Nexus Root Toolkit to Root, and surprisingly didn't lose any of my data!
Once again, Thanks for all the help everyone... You've all been quite helpful.

FYI the more up to date Recovery for 3.4 kernels

Update
arrrghhh's TWRP Q 2610 in my goodies.
Until Matt takes care of the 2.6 fix this is our best recovery for 4.3 roms. It is really not that hard to anticipate where to touch & you can touch & hold without activating a button to know where to touch.
Use with TWRP MANAGER is flawless!
Screen input requires the mirror of the buttons.
For normal use it only works if choosen from bootloader (abort to bootloader w/keys).
I am uploading the very zip from the twrp mounted SD while the phone is in recovery. BE CAREFULL....
Dim Screen perks up on after a time out.
Naming a BU in recovery-Impossible.
But twrp manager makes homescreen batch operation easy, SD usb mounting & 4.3 ready....
***********************************
The XT925/926 twrp can handle the needs of the new kernels.
Edit up'ed to goodies pg 2.
Update Twrp Mgr works well with the blind xt926 recovery!
Be sure to choose ext SD.
Use twrp mgr. For "remote control operation".:laugh:
Source:
http://forum.xda-developers.com/showpost.php?p=44930132&postcount=134
I can up a twrp flashable ver & it works but only from twrp manager- batch mode. The 926 graphics bork it for normal use.
Source: http://goo.im/devs/Hashcode/vanquish/twrp-2.6.0.0-recovery-vanquish.img

aviwdoowks said:
The XT925/926 twrp can handle the needs of the new kernels.
Edit up'ed to goodies pg 2.
Update Twrp Mgr works well with the blind xt926 recovery!
Be sure to choose ext SD.
Use twrp mgr. For "remote control operation".:laugh:
Source:
http://forum.xda-developers.com/showpost.php?p=44930132&postcount=134
I can up a twrp flashable ver & it works but only from twrp manager- batch mode. The 926 graphics bork it for normal use.
Source: http://goo.im/devs/Hashcode/vanquish/twrp-2.6.0.0-recovery-vanquish.img
Click to expand...
Click to collapse
Its a lot easier to use cwm or cwm touch or ouds that are actually built for our phone. Not to mention a lot safer.

ej1911 said:
Its a lot easier to use cwm or cwm touch or ouds that are actually built for our phone. Not to mention a lot safer.
Click to expand...
Click to collapse
These phones are siblings & this is a work around to have a working recovery for cm 4.3. The xt907 ver will not work!

All of the newer cwm variants work with 4.3. And they all have full graphical functionality with our phone.
I can't understand why you wouldn't recommend a solution that offers a fully working user interface when several exist.

ej1911 said:
All of the newer cwm variants work with 4.3. And they all have full graphical functionality with our phone.
I can't understand why you wouldn't recommend a solution that offers a fully working user interface when several exist.
Click to expand...
Click to collapse
In the above post
http://forum.xda-developers.com/showpost.php?p=44930132&postcount=134

Yes, I have seen that. It still does not answer the question of why you recommend a hacked up solution with TWRP when a much cleaner solution with CWM is available.
Sent from my Droid Razr M using xda app-developers app

ej1911 said:
Yes, I have seen that. It still does not answer the question of why you recommend a hacked up solution with TWRP when a much cleaner solution with CWM is available.
Sent from my Droid Razr M using xda app-developers app
Click to expand...
Click to collapse
The same reason I use rom manager on our M.
It is very handy.
Xt897 stock recovery is way better than ours.
Handy.
I backed up from the home screen & then restored from home screen with the xt926 ver.
Some posters on rzr could not get our recovery to succeed w/ 907 versions.

I don't claim to be an expert. I have been playing with Android since 1.6, and have been using UNIX and Linux based systems for over 2 decades, so I do have a decent working knowledge.
In that time, most of the expensive devices that I have seen turned into paperweights were caused by either using incorrect tools or using the correct tools without fully understanding how to use them.
I'm not trying to get into an argument, but I would suggest any user that has an interest in modifying their device learn how to use the tools that are required to do so. A working knowledge of fastboot, adb, basic Linux commands, factory and aftermarket recoveries, and RSD(or the manufacturers flashing tool for your device is the bare minimum anyone should have before rooting.
As far as 4.3 recoveries, I highly recommend switching to CWM at this point before playing. Dhacker has some available to download or you can build the newest (regular and touch) at the cwm builder site.
Sent from my Droid Razr M using xda app-developers app

Be careful. I forgot this was my recovery & started to do a 2 step from twrp mgr. Backup & flash the miui alpha! In a panic I used the keys to abort.

arrrghhh's TWRP Q 2610 in my goodies.
Until Matt takes care of the 2.6 fix this is our best recovery for 4.3 roms. It is really not that hard to anticipate where to touch & you can touch & hold without activating a button to know where to touch.
Use with TWRP MANAGER is flawless!
Screen input requires the mirror of the buttons.
For normal use it only works if choosen from bootloader (abort to bootloader w/keys).
I am uploading the very zip from the twrp mounted SD while the phone is in recovery. BE CAREFULL....
Dim Screen perks up on after a time out.
Naming a BU in recovery-Impossible.
But twrp manager makes homescreen batch operation easy, SD usb mounting & 4.3 ready....

are you rooted already ? (OPPO N1)

hello
I am courious
how many of us are rooted already ?
what method did you use to root your phone ?

nowy57 said:
hello
I am courious
how many of us are rooted already ?
what method did you use to root your phone ?
Click to expand...
Click to collapse
Rooted since long ago... On every build... All the time. :good:
If you're still having trouble with rooting CM or Omni, try the following.
You should be able to flash the SuperSU zip in TWRP after clearing Dalvik and Cache. If that fails, try below.
If you have SuperSU installed already and are failing to get root, you may have to remove your current SuperSU version. Don't just uninstall SuperSU! Go into SuperSU and go to "Settings". Scroll way down to "Full Unroot". Let that run as it needs to, then reboot into TWRP and wipe Cache and Dalvik. Then flash the SuperSU zip. Reboot to system. Test root.

sorry mate
it doesnt work to me
I have tried two times
as you wrote

Harfainx said:
Rooted since long ago... On every build... All the time. :good:
If you're still having trouble with rooting CM or Omni, try the following.
You should be able to flash the SuperSU zip in TWRP after clearing Dalvik and Cache. If that fails, try below.
If you have SuperSU installed already and are failing to get root, you may have to remove your current SuperSU version. Don't just uninstall SuperSU! Go into SuperSU and go to "Settings". Scroll way down to "Full Unroot". Let that run as it needs to, then reboot into TWRP and wipe Cache and Dalvik. Then flash the SuperSU zip. Reboot to system. Test root.
Click to expand...
Click to collapse
I have the same issue too. SuperSU installed 3 times. Did the full unroot like you said and reran the install after wiping both the cache. Still no root access.

I think that magic which found us oppo+CM team is missunderstand couse when I first time heard about cooperation this two companies I was so much happy .
by now when I have it I know that maybe couple of hundred is sold this phones and nobody cares about support it .
1.ROM straight from CM/OPPO site doesnt install propely via TWRP( without ingeration for user-script)
2.no root acces yet
this is sad true .
I v got note3 and I see more future with this phone
AOSP/CM is on a way - a lot of android entusiasts is working for free of charge about better and better ROMs
I am dissapointed - no offens to anybody

I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930

ChodTheWacko said:
I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930
Click to expand...
Click to collapse
it is not installed under CM ROM

It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk

ChodTheWacko said:
I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930
Click to expand...
Click to collapse
The exploit method was apparently patched in the official CM release. That exploit doesn't work.

Harfainx said:
It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
i am really confused couse I am pretty sure I am doing good as you said but no succes .

Harfainx said:
It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
If TWRP doesn't work properly how did you root? With the stock recovery?

it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .

nowy57 said:
it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .
Click to expand...
Click to collapse
You can indeed install straight from stock recovery. I did it last night. You have to use the official rom for the n1. Works nicely. I also had root working on cm. I flashed cm from stock recovery then used fastboot to install twrp. After twrp i flashed supersu zip. After i did the fix root or remove or whatever it is in the ap, reinstalled and tested it in titanium. Said i did have access but then went back to coloros to try and fix my mediascanner issue.
Sent from my N1 using XDA Premium 4 mobile app

nowy57 said:
it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .
Click to expand...
Click to collapse
I mean straight flash CM on the stock recovery, not on TWRP. You would have to be on the stock recovery for it to work straight from the CM download. On the stock recovery though, you will not be able to flash SuperSU on it. I do not believe that Omni can be flashed from there either, but I could be wrong (I haven't tried it).
There's a thread in the dev section that has the stock recovery hosted there. You can always fastboot flash back to that at any time.

Okay, I decided to install Cyanogenmod for the heck of it.
I already had TWRP 2.6.3.1 installed,
I downloaded and modified cm-10.2-WPPH50O-n1-signed.zip as per this page's instructions:
http://forum.xda-developers.com/showthread.php?t=2553165
I also downloaded supersu (current version is 1.86).
I entered TWRP and installed it, following that page's instructions.
After the install, I selected 'reboot'.
When I selected 'reboot', It prompted me with:
install superSU now? this will root your device.
I said no, and then rebooted back into TWRP.
Now back in TWRP, I install SUPERSU.
Now reboot again.
Now in CM.
Now run SuperSU, select 'settings', and unclick 'Respect CM root settings".
Now root works for me.
Two notes:
1) Respect CM root settings implies that in 'developer settings', there is some sort of "allow root" checkbox. I can't find it.
2) If, after the CM install, you answer 'install SuperSU' with YES", then it installs SuperSU, and reboots.
When you go back in, and run SuperSU, it says "gee, you aren't rooted, install SuperSU?"
If you answer THAT with yes, then it downloads some version of SuperSU, reboots into twrp, and installs it.
So it's kinda pointless answering YES in the first place, imho.

Are you serious right now?! I was worried unchecking Respect CM root setting would mess things up. But now I have root access. OMG... I unchecked it and it works! ^_^

57 43235953
ChodTheWacko said:
...
Two notes:
1) Respect CM root settings implies that in 'developer settings', there is some sort of "allow root" checkbox. I can't find it.
...
Click to expand...
Click to collapse
There is actually a #Superuser control panel just below "{} Developer option" that has lots of useful settings for root user control.
I haven't rooted yet but it seems like handy stuff for supersu to respect? Once you go into #Superuser use the menu button and you can add a profile etc it seems.
It's all kind of oddly done since adding that control panel after activating developer mode doesn't actually add an "su" binary.

hammerandtongs said:
There is actually a #Superuser control panel just below "{} Developer option" that has lots of useful settings for root user control.
I haven't rooted yet but it seems like handy stuff for supersu to respect? Once you go into #Superuser use the menu button and you can add a profile etc it seems.
It's all kind of oddly done since adding that control panel after activating developer mode doesn't actually add an "su" binary.
Click to expand...
Click to collapse
On what version of CM? or did you mean OMNI?
Under 'System' I only have:
Date & time
Accessibility
Developer options
Performance
About phone
Unless you meant 'in {} Developer' but I don't see anything in there either.
- Frank

ChodTheWacko said:
On what version of CM? or did you mean OMNI?
Under 'System' I only have:
Date & time
Accessibility
Developer options
Performance
About phone
Unless you meant 'in {} Developer' but I don't see anything in there either.
- Frank
Click to expand...
Click to collapse
WOW...so it literally disappeared as I was composing this message.
Cyanogenmod "signed" installed with the oppo bootloader (not rooted as supersu doesn't install successfully through bootloader etc).
Some kind of UI refresh after I changed some home screen settings?
It was persistent through 5-10x reboots and now is gone.
Obviously a glitch since I don't have su and I'm not truly rooted but it WAS there :\
I'd say its a bug to be filed if you are rooted and it's not available.

[Q] CM11 Milestone 5 release date? / CM11 Milestone 4 bugs/known problems? Thanks

Hello,
My LG G Pad 8.3 currently has the recent OTA Android 4.4.2 upgrade, nothing rooted/modded etc... Can someone let me know please:
1. When is CM11 Milestone 5 being released for the LG G Pad 8.3? I notice M5 was out a whie ago for other devices.
2. What are the known bugs/problems with CM11 M4?
3. Is it better to use CM11 M4 or the latest CM11 Nightly? I'm after a stable release, less so new features.
4. Are these good upgrade instructions? - http://true-android.blogspot.co.uk/2013/12/update-lg-g-pad-83-v500-to-android-442.html
Thank you

Is anyone able to help answer my questions please? Thanks

1) While the official CM11 did not do a M5 release, infected_ did an unofficial one.
http://forum.xda-developers.com/showthread.php?t=2660676
2/3) Not sure about M4 but infected_ M5 and near latest nightly (4/18) broke wifi on my device. Maybe that's why the official maintainers skipped the M5 release. I'm currently running the latest Mahdi-Rom.
http://forum.xda-developers.com/showthread.php?t=2581988
4) Use this instructions for 4.4.2 stock
http://forum.xda-developers.com/showpost.php?p=52092510&postcount=110

ruibing said:
1) While the official CM11 did not do a M5 release, infected_ did an unofficial one.
http://forum.xda-developers.com/showthread.php?t=2660676
Click to expand...
Click to collapse
Are you sure? - http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m5-release. Thanks btw.
ruibing said:
2/3) Not sure about M4 but infected_ M5 and near latest nightly (4/18) broke wifi on my device. Maybe that's why the official maintainers skipped the M5 release. I'm currently running the latest Mahdi-Rom.
http://forum.xda-developers.com/showthread.php?t=2581988
Click to expand...
Click to collapse
That's my worry. Even Cyanogenmod, which as I understand it has the highest quality control, it still breaks things.
LG's "attempt" at Android maybe pretty poor but at least everything works. Still CM11 isn't "Stable" yet.
* Is it worth waiting for a Release Candidate or Stable build or would you say M4 is stable? I appreciate probably tricky to answer. My concern is I go to all the effort and something crucial (like Wifi) no longer works. Currently my G Pad works perfectly (just using the poor LG software).
* I understand M4 is considered more stable than the latest Nightly right?
Thanks
ruibing said:
4) Use this instructions for 4.4.2 stock
http://forum.xda-developers.com/showpost.php?p=52092510&postcount=110
Click to expand...
Click to collapse
Great, thanks, will do.

The CM team did a blog post on their release process. Google "cm-11-m4-post-release-items"
The reason why device maintainers don't do a M release for a device is often a judgement call since M releases are not just tagged/renamed nightlies as of CM11. A M4 was released so I would give that a shot.
LG software was just too different for me. I'd prefer for the OS (and hardware) to disappear so that I can focus on using the apps, and LG does its best to remind me I'm using its product.
I would just backup stock kernel and recovery with flashify before flashing TWRP and then backing up your stock rom in TWRP before flashing to anything else.

ruibing said:
The CM team did a blog post on their release process. Google "cm-11-m4-post-release-items". A M4 was released so I would give that a shot.
Click to expand...
Click to collapse
Thanks. That's a really useful blog in explaining what a Milestone release is. I'll give M4 a go. My only concern is I just know M5 will come out shortly after. I'm only intending to do this 1-2 times if I can help it, second time preferably being Stable.
ruibing said:
LG software was just too different for me. I'd prefer for the OS (and hardware) to disappear so that I can focus on using the apps, and LG does its best to remind me I'm using its product.
Click to expand...
Click to collapse
True.
The only thing LG have added that's really much use is QPair and MySMS (free on Google Play) is better than that anyway. LG's G Pad interface needs refinement, the e-mail app is poor too. I don't mind OEM Android modifications as a general rule though. I'm perfectly happy with TouchWiz on my Galaxy S4.
ruibing said:
I would just backup stock kernel and recovery with flashify before flashing TWRP and then backing up your stock rom in TWRP before flashing to anything else.
Click to expand...
Click to collapse
Is it easy enough to backup the LG G Pad stock ROM so if need be I can revert back?
Finally when your best guess on CM11 Release Candidate or Stable? Obviously best guess only. Thanks again.

bradavon said:
Thanks. That's a really useful blog in explaining what a Milestone release is. I'll give M4 a go. My only concern is I just know M5 will come out shortly after. I'm only intending to do this 1-2 times if I can help it, second time preferably being Stable.
Click to expand...
Click to collapse
You mean M6? I don't they ever retroactively release builds.
bradavon said:
True.
The only thing LG have added that's really much use is QPair and MySMS (free on Google Play) is better than that anyway. LG's G Pad interface needs refinement, the e-mail app is poor too. I don't mind OEM Android modifications as a general rule though. I'm perfectly happy with TouchWiz on my Galaxy S4.
Click to expand...
Click to collapse
I do miss QRemote (IR blaster). It's the only thing you can't replace (at least not yet) on custom ROMs.
bradavon said:
Is it easy enough to back the LG G Pad stock ROM so if need be I can revert back?
Finally when your best guess on CM11 Release Candidate or Stable? Obviously best guess only. Thanks again.
Click to expand...
Click to collapse
You can go back by going to recovery and restoring your backup. If you backup your stock recovery in flashify, you can restore that too afterwards.
You may want to ask someone on the official or infected_ CM threads about the next RC/stable. However, the snapshots are pretty much monthly (within first two weeks of every month). So hopefully the maintainers decide to do the M6 release.

ruibing said:
You mean M6? I don't they ever retroactively release builds.
Click to expand...
Click to collapse
I probably do. I was thinking M5 for G Pad may still come but it's probably to late now. I'll wait to see if M6 appears before trying M4 now. M4 will be 2 months old by that point :-|
ruibing said:
I do miss QRemote (IR blaster). It's the only thing you can't replace (at least not yet) on custom ROMs.
Click to expand...
Click to collapse
I heard that. Thankfully I prefer using the original remote than a phone or tablet.
ruibing said:
You can go back by going to recovery and restoring your backup. If you backup your stock recovery in flashify, you can restore that too afterwards.
Click to expand...
Click to collapse
Ah so backing up your stock recovery and stock image are two different things?
ruibing said:
You may want to ask someone on the official or infected_ CM threads about the next RC/stable. However, the snapshots are pretty much monthly (within first two weeks of every month). So hopefully the maintainers decide to do the M6 release.
Click to expand...
Click to collapse
Thanks. Will do.

Hey, been runnig the M4 release for the last month, got an auto update to the m5, which ive been running for the last few weeks, been stable, no problems so far, no idea why the release isnt listed on the cyanogen site.

bradavon said:
Ah so backing up your stock recovery and stock image are two different things?
Click to expand...
Click to collapse
You usually override the stock recovery with TWRP (or CWM) before you reboot to recovery to backup then flash over your stock rom. In other words, you are backing up your stock rom through TWRP as your recovery, you've already lost your stock recovery. When you restore your stock rom, you will still have TWRP as your recovery. It may cause an issue if you try to install a future LG OTA update.
On the other hand, correct me if I'm wrong, but I believe you can use stock recovery backups from other users.

nibzzz said:
Hey, been runnig the M4 release for the last month, got an auto update to the m5, which ive been running for the last few weeks, been stable, no problems so far, no idea why the release isnt listed on the cyanogen site.
Click to expand...
Click to collapse
Thanks. That's great news. I may still wait for M6 now, not being long away now though. Definitely good to read though.
ruibing said:
You usually override the stock recovery with TWRP (or CWM) before you reboot to recovery to backup then flash over your stock rom. In other words, you are backing up your stock rom through TWRP as your recovery, you've already lost your stock recovery. When you restore your stock rom, you will still have TWRP as your recovery. It may cause an issue if you try to install a future LG OTA update.
Click to expand...
Click to collapse
And I can use Flashify instead of TWRP or CWM? Is Flashify stable/easy to use? Thanks again.

nibzzz said:
Hey, been runnig the M4 release for the last month, got an auto update to the m5, which ive been running for the last few weeks, been stable, no problems so far, no idea why the release isnt listed on the cyanogen site.
Click to expand...
Click to collapse
Could you let me know if you've had any problems with either M4 or M5 in these areas? -
1. Wireless
2. Bluetooth
3. GPS
4. Crashing
5. Slowness
5. Random Reboots
Thanks
p.s - Thanks for the screenshots. It's great to see the Multi-task button present and correct. I'm always using it and holding down Home is such a pain.

bradavon said:
Could you let me know if you've had any problems with either M4 or M5 in these areas? -
1. Wireless
2. Bluetooth
3. GPS
4. Crashing
5. Slowness
5. Random Reboots
Thanks
p.s - Thanks for the screenshots. It's great to see the Multi-task button present and correct. I'm always using it and holding down Home is such a pain.
Click to expand...
Click to collapse
Hey, no problems with wifi, I run Spotify with a set of bluetooth speakers off into problems, also no crashes or random reboots. I think it's def faster than stock rom and yes the standard buttons are sooo much better, but I think it's perceptibly slower compared to the nex 5, doesn't bother me though, il try post a benchmark later. Also flashify works great, it's not a substitute for Cwm or twrp, just let's you send and queue commands to recovery from an app, so u still need a custom recovery with it.

Antutu on cm11 m5, no other mods. looks pretty good! Interested to see the difference with stock rom? Could anyone post stock? Cheers!

nibzzz said:
Hey, no problems with wifi, I run Spotify with a set of bluetooth speakers off into problems, also no crashes or random reboots. I think it's def faster than stock rom and yes the standard buttons are sooo much better
Click to expand...
Click to collapse
Great stuff. Thank you again. I can wait a wee while longer for M6 now but will definitely be "upgrading".
nibzzz said:
Antutu on cm11 m5, no other mods. looks pretty good! Interested to see the difference with stock rom? Could anyone post stock? Cheers!
Click to expand...
Click to collapse
Are you running AnTuTu 4.4? Did you restart the G Pad before you ran the test? (I did). As oddly my LG G Pad 8.3 (UK Wifi Only model) running Android 4.4.2 OTA from LG (no mod/root or anything) is higher -
p.s - I'd expect the Nexus 5 to be faster, it's got a newer generation Snapdragon CPU.

Second run: 26917
Third run: 26172

bradavon said:
Great stuff. Thank you again. I can wait a wee while longer for M6 now but will definitely be "upgrading".
Are you running AnTuTu 4.4? Did you restart the G Pad before you ran the test? (I did). As oddly my LG G Pad 8.3 (UK Wifi Only model) running Android 4.4.2 OTA from LG (no mod/root or anything) is higher -
p.s - I'd expect the Nexus 5 to be faster, it's got a newer generation Snapdragon CPU.
Click to expand...
Click to collapse
Yep antutu 4.4, consistently get 25200's, not much higher, even after a reboot run, interesting that stock scores higher!

Now CM11 M6 is out, I have a few questions please:
1. Should I first install Flashify to backup my Stock Recovery?
2. If so, where do I find Flashify?
3. Then ClockworkMod Recovery?
4. Then perform a Nandroid backup using ClockworkMod Recovery?
5. If I did want to Restore my Original Stock ROM, is it simply a case of going into Recovery and restoring it?
I want to be sure I can revert back to exactly how my LG G Pad is now before installing CM11 M6. If I end up doing this, I'm overly bothered if I need to Factory Reset after/before restoring the stock image though.
Thanks

bradavon said:
Now CM11 M6 is out, I have a few questions please:
1. Should I first install Flashify to backup my Stock Recovery?
2. If so, where do I find Flashify?
3. Then ClockworkMod Recovery?
4. Then perform a Nandroid backup using ClockworkMod Recovery?
5. If I did want to Restore my Original Stock ROM, is it simply a case of going into Recovery and restoring it?
I want to be sure I can revert back to exactly how my LG G Pad is now before installing CM11 M6. If I end up doing this, I'm overly bothered if I need to Factory Reset after/before restoring the stock image though.
Thanks
Click to expand...
Click to collapse
1) Always good idea to backup everything. If you backup your stock recovery before installing a new recovery image, it makes going back to full stock easier.
2) It's on the app store.
3) I don't think CWM supports this tablet anymore. Use TWRP 2.7.0.1
4) Yes, backup your system, data, and boot, then do a factory reset (in TWRP), and then flash the new rom.
5) Yes. Then if you want to restore the stock recovery (if you backed it up), do it through flashify.
---------- Post added at 11:23 AM ---------- Previous post was at 11:18 AM ----------
Here's the exact process I went through (I posted it somewhere awhile ago). Keep in mind I came from stock 4.2.2. If you come from stock 4.4.2, you need to use the ioroot method to root.
0) Download custom rom, twrp, and gapps to SD card
1) Rooted it using Kingo Android Root
2) Installed flashify
3) Backed up stock recovery using flashify
4) Flashed TWRP recovery using flashify
5) Rebooted to recovery
6) Backed up boot, system, and data
8) Wipe data, cache, etc (factory reset)
7) Flashed custom rom then gapps
9) Wipe cache
10) Reboot
Restore
0) Reboot to recovery
1) If you want to backup your custom rom, back up boot, system, and data
2) Restore boot, system, and data from your stock backup
3) Wipe cache
4) Reboot
5) If you want to restore stock recovery, restore using flashify
6) If you want to unroot, either use the root tool or flash back to stock 4.2.2 (http://forum.xda-developers.com/showthread.php?p=51466025)

ruibing said:
2) It's on the app store.
Click to expand...
Click to collapse
Firstly thanks for such a detailed and helpful post.
This is Flashify right? - https://play.google.com/store/apps/details?id=com.cgollner.flashify
ruibing said:
Keep in mind I came from stock 4.2.2. If you come from stock 4.4.2, you need to use the ioroot method to root.
Click to expand...
Click to collapse
Yes I've upgraded my G Pad OTA from 4.2.2 to 4.4.2, so noted thanks. Do you have to root the G Pad? This guide doesn't mention it:
http://true-android.blogspot.co.uk/2013/12/update-lg-g-pad-83-v500-to-android-442.html
It even says: "NOTE: Root is turned off by default in CM ROMs". Although I see I'd need to root for Flashify anyway.
ruibing said:
6) If you want to unroot, do a factory reset (in the settings menu)
Click to expand...
Click to collapse
It's really that simple?
Thanks again.