I'll post my question after some background:
I was on CWM Touch, downloaded and installed the TWRP from google play. Rebooted into recovery, created backups to internal and external, and flashed SkyICS 4.2f6 by Seanz. I followed OP instructions on how to flash. Did not have any problems and it was very easy to use.
Used TWRP and flashed several MODS and ROM updates without any hitch. All I did was reboot into recovery selected the zip files and swipe to install, did not even had to wipe cache or anything. I am not sure if this is the correct way but I was able to do so without any problems.
I wanted to install the same rom but to do a clean wipe since the rom had several updates. So, I rebooted into TWRP recovery, did OP flashing instructions which were:
-reboot into team win recovery
-wipe system
-factory data reset
-then go to mounts and choose external sd
-no go back and find the rom by choosing install zip
-swipe to confirm
-then install the radio you downloaded
and when complete reboot phone
-at this point everything will be settling and caching
which may or may not seem laggy.... and yes that white line is normal
its a battery representation mod
-im sure youll be eager to update busybox immediatly but let me tell you no
first open super user app.. find preferences and update user binary
hit it twice giving it root permissions
now .. is when to update busy box through the provided installer
-after you have done this
-power down phone
reboot into recovery and flash the latest update
and email package only
However, I was not able to reboot into recovery. I have a Samsung Skyrocket but was not able to put the phone into recovery mode by pressing and holding the power, volume up, and volume down buttons. The phone kept vibrating but the Samsung screen wont come up. Frustrated, I rebooted the phone, downloaded CWM, updated to Touch and proceeded to flash using CWM with no problems.
At this point i'm hesitant on using TWRP. I am not even sure if ODIN supports it. I'm afraid that if i'm on TWRP and brick my phone, I will not be able to use ODIN.
Questions:
Has anyone encounter the same problem?
Is TWRP compatible with ODIN?
Can anyone using Samsung Skyrocket confirm the recovery steps used above is correct?
Thank you for your help.
i am currently using twrp and ive had no problems flashing roms including sky ics which those directions are from also a recovery isnt compatible with odin if you want to odin back to stock or flash anew recovery image you just go into download mode and procedd from there
RAVEN6 said:
I'll post my question after some background:
I was on CWM Touch, downloaded and installed the TWRP from google play. Rebooted into recovery, created backups to internal and external, and flashed SkyICS 4.2f6 by Seanz. I followed OP instructions on how to flash. Did not have any problems and it was very easy to use.
Used TWRP and flashed several MODS and ROM updates without any hitch. All I did was reboot into recovery selected the zip files and swipe to install, did not even had to wipe cache or anything. I am not sure if this is the correct way but I was able to do so without any problems.
I wanted to install the same rom but to do a clean wipe since the rom had several updates. So, I rebooted into TWRP recovery, did OP flashing instructions which were:
-reboot into team win recovery
-wipe system
-factory data reset
-then go to mounts and choose external sd
-no go back and find the rom by choosing install zip
-swipe to confirm
-then install the radio you downloaded
and when complete reboot phone
-at this point everything will be settling and caching
which may or may not seem laggy.... and yes that white line is normal
its a battery representation mod
-im sure youll be eager to update busybox immediatly but let me tell you no
first open super user app.. find preferences and update user binary
hit it twice giving it root permissions
now .. is when to update busy box through the provided installer
-after you have done this
-power down phone
reboot into recovery and flash the latest update
and email package only
However, I was not able to reboot into recovery. I have a Samsung Skyrocket but was not able to put the phone into recovery mode by pressing and holding the power, volume up, and volume down buttons. The phone kept vibrating but the Samsung screen wont come up. Frustrated, I rebooted the phone, downloaded CWM, updated to Touch and proceeded to flash using CWM with no problems.
At this point i'm hesitant on using TWRP. I am not even sure if ODIN supports it. I'm afraid that if i'm on TWRP and brick my phone, I will not be able to use ODIN.
Questions:
Has anyone encounter the same problem?
Is TWRP compatible with ODIN?
Can anyone using Samsung Skyrocket confirm the recovery steps used above is correct?
Thank you for your help.
Click to expand...
Click to collapse
To reboot into recovery you hold power, volume up and down and when you see the first samsung logo let go of the power or it will keep rebooting.
As for being compatible with odin, I'm not sure what you mean. You can flash TWRP through odin, you can get into download mode with twrp installed also.
Have you tried reinstalling TWRP?
got the phone yesterday, then installed the OTA update , then when i got back home i unlocked the bootloader from htcdev site.Then went to fastboot and flashed the cwm recovery touch,installed the su libs, did a backup ,factory reset and wipe cache, installed cm 10.0 and gapps , after restart it was unable to boot.now i know this is because of s-on.So i restored the backup and then installed goo manager from play store and flashed twrp recovery in order to try cm 10.1 with its aroma installer.during the installation of cm 10.1 i choose the newest tmo radio and after that i installed the htcdumlock and then THIS IS WHERE THE THINGS WENT WRONG i choose one of the other options in twrp i think restore recovery and then the option on the right side on the screen but it didn't able to finish it so i restarted the phone and now it stays on the the red warning text , unless i install boot.img from MaximusM fastboot toolkit or something witch gives me the option to choose recovery from fastboot witch actually somehow boots the ROM. forgot to mention that i had problems with the sd card mounting under twrp after i flashed cm 10.1 so i had to revert back and then between stock recovery witch actually makes the phone to boot in the stock rom and the other two custom recovery`s
so i have downloaded the tmo ruu and before im trying to relock the device i just want to ask am i on the right way with this??
Its OK i figured it out
Hi guys,
I'm running my Moto G 16GB on Kitkat 4.4.2 system version 175.44.1.falcon_umts.Retail.en.DE. Today it offered to download and install the latest OTA update (called 176.44.1.en.DE). I started the download and tried to install it.
After downloading the update was placed in /cache. The file name was 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE.zip', which surprised me. I was expecting something like 'Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip'.
When I tried to install it without removing root and without going back to stock recovery it ended with a signature error in CWM. Installing the untrusted zip manually didn't work as well - as expected.
Then I tried to follow advise from other threads and went back to stock recovery (extracted from a full install package 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE' - 444MB) That seemed to work and the install of the OTA update went fine before getting stuck on the boot animation on the first boot. It sat there for 10 minutes before I rebooted and restored a CWM backup.
I'm running out of ideas. Some say it's sufficient to go back to stock recovery temporarily. Others say you need to go back to full stock.
I have to repeat that I'm rooted and that I've de-activated a few unused apps (mainly harmless google stuff (hangout, search, music and so on) and Motorola Assist, Migrate and 'Context Services') .
Are there further findings about what stops the OTA from succeeding?
Many thanks in advance,
Kleo2
Kleo2 said:
Hi guys,
I'm running my Moto G 16GB on Kitkat 4.4.2 system version 175.44.1.falcon_umts.Retail.en.DE. Today it offered to download and install the latest OTA update (called 176.44.1.en.DE). I started the download and tried to install it.
After downloading the update was placed in /cache. The file name was 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE.zip', which surprised me. I was expecting something like 'Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip'.
When I tried to install it without removing root and without going back to stock recovery it ended with a signature error in CWM. Installing the untrusted zip manually didn't work as well - as expected.
Then I tried to follow advise from other threads and went back to stock recovery (extracted from a full install package 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE' - 444MB) That seemed to work and the install of the OTA update went fine before getting stuck on the boot animation on the first boot. It sat there for 10 minutes before I rebooted and restored a CWM backup.
I'm running out of ideas. Some say it's sufficient to go back to stock recovery temporarily. Others say you need to go back to full stock.
I have to repeat that I'm rooted and that I've de-activated a few unused apps (mainly harmless google stuff (hangout, search, music and so on) and Motorola Assist, Migrate and 'Context Services') .
Are there further findings about what stops the OTA from succeeding?
Many thanks in advance,
Kleo2
Click to expand...
Click to collapse
If your phone is rooted or there is a CWM installed or there is any change in system files then ota will fail till you flash stock rom. You can't just bring back stock recovery. You have to "delete" root as well.
There is some info http://forum.xda-developers.com/showpost.php?p=47495650&postcount=6
I will post my case here, I had the same problem, I had CWM and root and when I rebooted to update I get installation failed and boot loop.
Then I just flashed stock recovery (only) rebooted and now I already have the update installed
CromoPT said:
I will post my case here, I had the same problem, I had CWM and root and when I rebooted to update I get installation failed and boot loop.
Then I just flashed stock recovery (only) rebooted and now I already have the update installed
Click to expand...
Click to collapse
Hi, thanks for your replies. Because of your report and others, who state the same (installing stock recovery only to get the update working) I was hoping to get around going back to full stock. It always takes a lot of time to configure the phone the way it was configured before essentially wiping.
Just to repeat what I did: when I try to install the OTA while CWM is installed there's just an error message in CWM, the update fails, but the phone is working normally afterwards. It's just not updated.
When I try with stock recovery the update process finishes without errors, but the phone get stuck during the boot animation.
Maybe there's a way to fix the boot loop?
Looking forward to any suggestions
Cheers, Kleo2
I tried again and found a way without going back to full stock.
1. flashed stock recovery from full 175.44.1 image
2. let the phone download the OTA and restart to install it
3. ota install in stock recovery went fine
4. reboot -> stuck on boot animation again
5. flashed CWM and wiped cache AND dalvik cache
6. next boot took longer than normal but got past the boot animation
7. android optimized/cached my apps and then started normally
8. version is now 176.44.1 and the phone seems to work normally (after 30 minutes of usage)
Hope that helps someone and that I won't have issues going forward because I did it this way.
Cheers, Kleo2
Kleo2 said:
I tried again and found a way without going back to full stock.
Click to expand...
Click to collapse
Thanks. :good: Did 1 to 3 and phone booted just fine (not stuck on boot animation)
My phone: No logo fix, root, Xposed Framework
After update root was still there, Xposed needed a new install
total noob
i would so much like to update my rooted moto g.. because of my card reader.
does anyone know a step-by-step-for-complete-noobs-post and could provide a link?
i'm just starting.. and so happy and proud that i got my phone rooted.. and that i got rid of this rebooting problem by erasing the cache.
but i'm already lost when i read "flashed stock recovery".. yeah i know: that much noob!
help would be much appreciated!
Papshmir
Papshmir said:
i would so much like to update my rooted moto g.. because of my card reader.
does anyone know a step-by-step-for-complete-noobs-post and could provide a link?
i'm just starting.. and so happy and proud that i got my phone rooted.. and that i got rid of this rebooting problem by erasing the cache.
but i'm already lost when i read "flashed stock recovery".. yeah i know: that much noob!
help would be much appreciated!
Papshmir
Click to expand...
Click to collapse
I UPDATED my rooted Kitkat Tesco version SUCCESFULLY! and still rooted.
What I did:
1. install Motorola Device Manager (RESTART computer and telephone)
2. downloaded MotoTool
3. Made a Nandroid backup in CMW, made a backup with MotoTool too. Just in case
And deactived (did not uninstall) my Xposed framework modules (if you dont have it, you dont need to)
I have some system apps disabled, but didnt re-activate it. (was too lazy haha)
4. downloaded the correct ROM from: http://sbf.droid-developers.org/phone.php?device=14 (Tesco UK 4.4.2)
5. unzipped the ROM and rename and overwrite the recovery.img to the exact name as in the MotoTool All In One 2.6\Data\KitKat\StockKitKatrecovery.img (Just for sure it's the same as my ROM, I dont know if all the ROMs have the same recovery sooo )
6. started MotoTool, unplug&replug device. Checked KitKat option in the program, did a connection check, it was okay. Did a NORMAL restart via progam. You have to grant permisson on your phone.
7. after reboot, rebooted the phone to FASTBOOT.
8. Checked Stock Fastboot in the program, it flashed succesfully. Then I went into recovery (1×down volume, then 1× up volume) checked if the recovery was working. It was working (android logo+ no command error message)
9. reboot (long press power button)
10. Updeted OTA, settings/inf./update.. blabla okay okay next next. Wait until it downloads (only 7.9 MB )
11. wait for the update to be done, then it reboots, then apps are being updated. Everything looks fine and working
+1 flash CMW or other recovery again.
Hope this helps! I was afraid to do it too. I'm not used to MotoTool and other Motorola stuff because I had a HTC Desire, it was much simplier with that. But no risk here either! Good luck!
So I am trying to put back my stock recovery so I can take the OTA, but after I flash the recovery and try to reboot to it, it says "No Command". I have reflashed TWRP and then the stock recovery again with the same result. The phone itself will boot fine, but I can't install the OTA as it gets an error part of the way into the install. Any ideas? I have the 1034.
EDIT: Well I remembered I did the H+ mod, so after reverting that the OTA flashed I had Faux Kernel before hand, but after reflashing it my wi-fi wont enable, any ideas?
Thanks!
Kleo2 said:
I tried again and found a way without going back to full stock.
1. flashed stock recovery from full 175.44.1 image
2. let the phone download the OTA and restart to install it
3. ota install in stock recovery went fine
4. reboot -> stuck on boot animation again
5. flashed CWM and wiped cache AND dalvik cache
6. next boot took longer than normal but got past the boot animation
7. android optimized/cached my apps and then started normally
8. version is now 176.44.1 and the phone seems to work normally (after 30 minutes of usage)
Hope that helps someone and that I won't have issues going forward because I did it this way.
Cheers, Kleo2
Click to expand...
Click to collapse
Thanks,
Wiping cache and dalvik cache did the trick for me. You saved my day
Please please help
I have the same problem. I've tried to update the new OTA and failed. After restoring full stock rom, the system simply doesn't boot!
I had Faux Kernel and GravityBox but I didn't revert anything. I thought that a full stock rom would clear all system settings.
This is my version of stock (Blur_Version.174.44.9.falcon_umts.Retail.en.GB) and I tried to flash it several times now. No success. I get stuck on the boot logo.
I tried to downgrade to 4.3 using version Blur_Version.14.71.8.falcon_umts.Retail.en.GB. I was able to boot and see the initial setup but I have no WIFI! I was trying to install 4.3 then try to update via OTA but OTA only works with WIFI so I'm stuck.
I also tried installing the 24th Feb nightly build of Cyanogen and the device also booted but with no WIFI.
I really don't know what to do! Please help me. I've tried other stock images out of despair but none with sucess.
Does anyone have a clue to what might be to problem and how to revert it?
Thank you
draco259 said:
So I am trying to put back my stock recovery so I can take the OTA, but after I flash the recovery and try to reboot to it, it says "No Command". I have reflashed TWRP and then the stock recovery again with the same result. The phone itself will boot fine, but I can't install the OTA as it gets an error part of the way into the install. Any ideas? I have the 1034.
EDIT: Well I remembered I did the H+ mod, so after reverting that the OTA flashed I had Faux Kernel before hand, but after reflashing it my wi-fi wont enable, any ideas?
Click to expand...
Click to collapse
Before flashing stock ROM try to clear/format all your partitions with a custom recovery!
Sent from my XT1032 using xda app-developers app
I installed the OTA update using the CWM recovery but not root, I changed the update-script to not give error during installation
Hui91 said:
I UPDATED my rooted Kitkat Tesco version SUCCESFULLY! and still rooted.
What I did:
1. install Motorola Device Manager (RESTART computer and telephone)
2. downloaded MotoTool
3. Made a Nandroid backup in CMW, made a backup with MotoTool too. Just in case
And deactived (did not uninstall) my Xposed framework modules (if you dont have it, you dont need to)
I have some system apps disabled, but didnt re-activate it. (was too lazy haha)
4. downloaded the correct ROM from: http://sbf.droid-developers.org/phone.php?device=14 (Tesco UK 4.4.2)
5. unzipped the ROM and rename and overwrite the recovery.img to the exact name as in the MotoTool All In One 2.6\Data\KitKat\StockKitKatrecovery.img (Just for sure it's the same as my ROM, I dont know if all the ROMs have the same recovery sooo )
6. started MotoTool, unplug&replug device. Checked KitKat option in the program, did a connection check, it was okay. Did a NORMAL restart via progam. You have to grant permisson on your phone.
7. after reboot, rebooted the phone to FASTBOOT.
8. Checked Stock Fastboot in the program, it flashed succesfully. Then I went into recovery (1×down volume, then 1× up volume) checked if the recovery was working. It was working (android logo+ no command error message)
9. reboot (long press power button)
10. Updeted OTA, settings/inf./update.. blabla okay okay next next. Wait until it downloads (only 7.9 MB )
11. wait for the update to be done, then it reboots, then apps are being updated. Everything looks fine and working
+1 flash CMW or other recovery again.
Hope this helps! I was afraid to do it too. I'm not used to MotoTool and other Motorola stuff because I had a HTC Desire, it was much simplier with that. But no risk here either! Good luck!
Click to expand...
Click to collapse
At part 8, I am getting an image of the android guy with his stomach open with a big red '!'. That's 'no command' right?
Any ideas? I have no idea what I am doing
Guys, a really easy way to update is:
1. Install Philz recovery - http://forum.xda-developers.com/showthread.php?t=2639583
2. Reboot and then download the OTA update when prompted - select Install when prompted
3. It will now reboot into Philz recovery, install the update and reboot
4. You'll see Android is Upgrading...
5. Re-boot back into recover and re-install faux kernel
I have just upgraded my XT1032 on 174.44.9 en GB (rooted + faux008) to 176.44.1 using this... worked like a dream! All I had to do was re-install faux kernel as that was overwritten by the OTA, but Root was in-tact...
i have root, twrp recovery and faux kernel, the problem is only faux kernel? Or I must remove all? (root recovery etc)
Ive been trying to install katkiss lollipop 5.0 on my tf101 but every time it comes up with errors that leaves my tablet bricked i think i need to update my recovery ive got teamwin 2.6 how do i fix this or update my recovery pls give a detailed guide
Timmieh14 said:
update my recovery
Click to expand...
Click to collapse
download TWRP 2.8.1.1 zip for TF101.
Boot into recovery and choose 'Install'
search for your downloaded signed_twrp-2.8.1.1_tf101.zip and flash it.
I assume you have no working ROM installed, so this part is a bit different from normal
Now choose 'Reboot'(a warning pops up that no ROM is installed), and don't install root (we do that later).
While rebooting, you will notice a progressbar. When the progressbar is finished, you have to force a reboot to the recovery (since you are without a working ROM, nothing else will work anyway).
you should now have twrp 2.8.1.1 (look in the statusbar on top of the screen)
from here it is straight forward:
flash Katkiss, Supersu and gapps in that order.
if things still does not work I find it useful to format data (not just wipe). especially useful when coming from another ROM
Hello guys,
first off: i had something to do in the past with all this stuff but my memory isnt that great anymore so please correct me if im wrong
so here's the thing: my OPO decided to not detect my SIM anymore, so i did a factory reset thru recovery. I also rooted the phone before with a video tutorial from youtube (don't know if i can link it here this is my first post^^). What it does is install SuperSU over TWRP. You then have root without erasing your data! I was kinda surprised because i read in other threads that it actually will.
But anyways back to topic. I am now on these settings:
Cyanogen OS 12.1.1-Y0G7DAS2K1
Stock Recovery
Rooted
Bootloader unlocked (not sure, but i guess otherwise it wouldnt work)
I received a message for the OTA Update to Cyanogen OS 13. Downloaded & installed it, phone reboots into recovery. Already surprised here because its not TWRP anymore but i guess it was just temporary for the root installing. Or maybe it was because i didn't unchecked the "update recovery" checkbox in developer options, i think its active on default.
But anyways, the recovery tries to install it and suddenly the menu shows up again with an android in the background (in his chest is a red warning sign). No error, just the graphical android in the background. After a restart, nothing changed still on the same version. I did a factory reset once more and also "deleted media" and wiped cache.
As i mentioned, im not up-to-date with the differences on CyanogenMod and Cyanogen OS.
What i want to do now:
Step 1: Format my OPO as clean as possible.
Is Factory Reset and wipe media etc. enough for this? Or do i have to hard reset it?
Step 2: Root Access and TWRP.
I lost both of these after an OTA update to my OPO. I guess it was when i received the Cyanogen OS update. I would like to know when exactly these two will be erased and what to do to not lose them anymore. I heard it differs between CM and Cyanogen OS.
Step 3: Decision what OS to use: CyanogenMod or Cyanogen OS?
Im willing to wait for updates as long as they're stable. And i would also prefer to just install them over OTA (when it works^^). I don't want to flash like crazy, i only want a steady, rooted, customizable OS. I searched on this forum but im not sure which are the latest versions of both and what the differences are. What would you suggest me on these preferences?
Step 4: Restoring my Data
I backed up my Apps with Titanium Backup and transfered the folder to my PC. Never used it before, so i would like to know if it can cause any problems if i restore it on a newer version of Cyangogen OS or even Cyanogenmod?
Hope i don't forget anything. Sorry for the long post & noob questions you probably read everyday
EagleJR said:
Hello guys,
first off: i had something to do in the past with all this stuff but my memory isnt that great anymore so please correct me if im wrong
so here's the thing: my OPO decided to not detect my SIM anymore, so i did a factory reset thru recovery. I also rooted the phone before with a video tutorial from youtube (don't know if i can link it here this is my first post^^). What it does is install SuperSU over TWRP. You then have root without erasing your data! I was kinda surprised because i read in other threads that it actually will.
But anyways back to topic. I am now on these settings:
Cyanogen OS 12.1.1-Y0G7DAS2K1
Stock Recovery
Rooted
Bootloader unlocked (not sure, but i guess otherwise it wouldnt work)
I received a message for the OTA Update to Cyanogen OS 13. Downloaded & installed it, phone reboots into recovery. Already surprised here because its not TWRP anymore but i guess it was just temporary for the root installing. Or maybe it was because i didn't unchecked the "update recovery" checkbox in developer options, i think its active on default.
But anyways, the recovery tries to install it and suddenly the menu shows up again with an android in the background (in his chest is a red warning sign). No error, just the graphical android in the background. After a restart, nothing changed still on the same version. I did a factory reset once more and also "deleted media" and wiped cache.
As i mentioned, im not up-to-date with the differences on CyanogenMod and Cyanogen OS.
What i want to do now:
Step 1: Format my OPO as clean as possible.
Is Factory Reset and wipe media etc. enough for this? Or do i have to hard reset it?
Step 2: Root Access and TWRP.
I lost both of these after an OTA update to my OPO. I guess it was when i received the Cyanogen OS update. I would like to know when exactly these two will be erased and what to do to not lose them anymore. I heard it differs between CM and Cyanogen OS.
Step 3: Decision what OS to use: CyanogenMod or Cyanogen OS?
Im willing to wait for updates as long as they're stable. And i would also prefer to just install them over OTA (when it works^^). I don't want to flash like crazy, i only want a steady, rooted, customizable OS. I searched on this forum but im not sure which are the latest versions of both and what the differences are. What would you suggest me on these preferences?
Step 4: Restoring my Data
I backed up my Apps with Titanium Backup and transfered the folder to my PC. Never used it before, so i would like to know if it can cause any problems if i restore it on a newer version of Cyangogen OS or even Cyanogenmod?
Hope i don't forget anything. Sorry for the long post & noob questions you probably read everyday
Click to expand...
Click to collapse
Ok so first you can not perform OTA updates with a custom recovery like TWRP. So if you want OTA updates don't install a custom recovery. You lost TWRP before even performing the OTA update don't know how but you did. So I am going to instruct you how to start fresh.
1. You need ADB and fastboot installed you can get the minimal version here http://forum.xda-developers.com/showthread.php?t=2317790 or you can get the full SDK manager which has fastboot and adb https://developer.android.com/studio/index.html but if your not planning development just go with minimal.
2. Follow this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 You don't need to do step 4 since you want to install a custom recovery. So just reboot after you flash all the stock files.
(Also make sure you download the right stock rom he has a 16gb and a 64gb listed. Or you can download the stock rom straight from cynogen os here https://cyngn.com/support
3. Next you will need the TWRP file you can get it here https://dl.twrp.me/bacon/ if you don't have ADB/Fastboot in your path just place the file in the same folder as your fastboot. Also rename the file to recovery.img make sure you don't name it recovery.img.img
4. Download SUPERSU for root get it here https://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
5. With your phone on plug it in to your computer and transfer the SuperSU zip to the download folder on your phone.
6. Unplug your phone and reboot to fastboot then plug your phone back in
7. Open command prompt in the fastboot folder by holding shift and right click and select open command window here.
8. Type fastboot devices (This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.)
9. Type Fastboot Flash recovery recovery.img
10. Once the flash is done don't let the phone fully boot to system or it will rewrite to the stock recovery so hold the power button and volume down and it will boot into TWRP recovery. IF you let it boot into the system and it does reinstall the stock recovery you will need to re-install twrp
11. Once in twrp perform a backup of your stock rom
12. After the backup is done go back to the main menu of TWRP go to install navigate to the download file and then install SuperSU
13. Now reboot and you now have the stock rom with root and a custom recovery.
14. Difference between cynogen os and cynogenmod http://www.androidcentral.com/difference-between-cyanogen-os-and-cyanogenmod
Hope this helps and
Durso81 said:
Ok so first you can not perform OTA updates with a custom recovery like TWRP. So if you want OTA updates don't install a custom recovery. You lost TWRP before even performing the OTA update don't know how but you did. So I am going to instruct you how to start fresh.
1. You need ADB and fastboot installed you can get the minimal version here http://forum.xda-developers.com/showthread.php?t=2317790 or you can get the full SDK manager which has fastboot and adb https://developer.android.com/studio/index.html but if your not planning development just go with minimal.
2. Follow this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 You don't need to do step 4 since you want to install a custom recovery. So just reboot after you flash all the stock files.
(Also make sure you download the right stock rom he has a 16gb and a 64gb listed. Or you can download the stock rom straight from cynogen os here https://cyngn.com/support
3. Next you will need the TWRP file you can get it here https://dl.twrp.me/bacon/ if you don't have ADB/Fastboot in your path just place the file in the same folder as your fastboot. Also rename the file to recovery.img make sure you don't name it recovery.img.img
4. Download SUPERSU for root get it here https://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
5. With your phone on plug it in to your computer and transfer the SuperSU zip to the download folder on your phone.
6. Unplug your phone and reboot to fastboot then plug your phone back in
7. Open command prompt in the fastboot folder by holding shift and right click and select open command window here.
8. Type fastboot devices (This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.)
9. Type Fastboot Flash recovery recovery.img
10. Once the flash is done don't let the phone fully boot to system or it will rewrite to the stock recovery so hold the power button and volume down and it will boot into TWRP recovery. IF you let it boot into the system and it does reinstall the stock recovery you will need to re-install twrp
11. Once in twrp perform a backup of your stock rom
12. After the backup is done go back to the main menu of TWRP go to install navigate to the download file and then install SuperSU
13. Now reboot and you now have the stock rom with root and a custom recovery.
14. Difference between cynogen os and cynogenmod http://www.androidcentral.com/difference-between-cyanogen-os-and-cyanogenmod
Hope this helps and
Click to expand...
Click to collapse
Thank you very much! I did all of your Instructions step-by-step and it worked flawless. Im now on the latest CM13 Release. I hope it was the right decision and it runs smooth and stable. And if not i got the backup I do have 2 more questions:
-TWRP asked me if i want to let them "modify my partition". It helps when you are getting official updates. Is that important for me? I guess i will just flash future updates over recovery and not over OTA anyways, so i can left this "modify" option unchecked, right?
-While i did the factory reset, it said that most of the time i will not have to delete internal storage. Does that mean it also excludes private stuff like photos, videos & also backups from titanium & TWRP (if it's the same stored location)? Thank you again for anything
EagleJR said:
Thank you very much! I did all of your Instructions step-by-step and it worked flawless. Im now on the latest CM13 Release. I hope it was the right decision and it runs smooth and stable. And if not i got the backup I do have 2 more questions:
-TWRP asked me if i want to let them "modify my partition". It helps when you are getting official updates. Is that important for me? I guess i will just flash future updates over recovery and not over OTA anyways, so i can left this "modify" option unchecked, right?
-While i did the factory reset, it said that most of the time i will not have to delete internal storage. Does that mean it also excludes private stuff like photos, videos & also backups from titanium & TWRP (if it's the same stored location)? Thank you again for anything
Click to expand...
Click to collapse
The only way you can do official updates is to follow all the steps above and flashing the newest stock ROM via fastboot and reinstalling twrp. Now if you want to flash a custom ROM like cynogenmod then you can just download the latest ROM from cynogemod and install it via twrp. As far as your pics go I would either upload them to a cloud service or your PC before switching ROMs. For your apps yes just backup with titanium backup and then just restore them when you change ROMs.