Hi All, This is my first official post on XDA. If you find any errors/corrections to be made, please point it out. All corrections are welcomed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING: Proceed on your own risk, Neither I nor any XDA member is responsible for your actions. Failure to follow instructions MAY brick your device and render it unusable.
This Guide will also work for any other variant of Moto X, instead of using TWRP 2.6.3.1, you can use any version of TWRP. For some reason, any other version of TWRP causes errors on the Moto X XT1052.
First some, pre-requisites for installing CM 12 on your Moto X XT1052:
1.) Unlocked Bootloader (doing this will factory reset your device)
2.) Rooted [Optional]
3.) TWRP Custom Recovery v2.6.3.1 Installed. No other version will work!
Instructions: (This assumes your are on stock Moto ROM, will a locked BootLoader and No Custom Recovery Installed. If not, Jump to Step 3.)
1. Follow this great guide at Elemental X to Unlock your BootLoader
2. Continue to follow the guide at Elemental X to install TWRP v2.6.3.1 however, install version 2.6.3.1 [Download it from here]
3. For CM 12 to work, we will first have to install CM 11 and complete a first boot. Follow the following instructions to flash CM 11 first:
A. Download CM 11 ROM for MOTO X (Ghost) [ Download Here ]
B. Transfer to SD Card and Boot into TWRP recovery [Make sure it is v2.6.3.1]
C. Head into Wipe and Factory Reset your Phone
D. Wipe Cache and Dalvik Cache
E. Then head into install and install the CM 11 zip file (No need to flash GAPPs yet).
F. Once done, perform one complete reboot
4. Now we install CM 12:
A. Download the latest version of CM 12 Ghost [Download here]
B. Download Latest GAPPS [Download Here]
C. Transfer files to SD Card
D. Boot into TWRP recovery and perform another complete Wipe
E. Install CM 12 .zip and the GAPPS .zip
F. Perform the first boot (May take anywhere from 1 - 5 mins, for the first boot only)
5. Voila! You're done.
How to update to the latest NIGHTLY: (Basically dirty flashing, will NOT erase your data)
1. Download the latest nightly using CMUpdater
2. Boot into recovery
3. Wipe Dalvik Cache and Cache
4. Install the .zip from /sdcard/cmupdater/
5. Reboot and let Android perform application compilation.
Let me know if you run into any error! Happy Flashing!
DON'T FORGET TO GIVE ME A THANKS! :laugh:
Thank but...
How to push rom zip file into the SD Card, the ADB sideload didn't work and i can't reboot on OS
Just recovery work
xav314 said:
How to push rom zip file into the SD Card, the ADB sideload didn't work and i can't reboot on OS
Just recovery work
Click to expand...
Click to collapse
Well if your system can recognize your phone while in Recovery, all you have to do is transfer the zip into your internal storage. If your system can't detect your phone, then you'll probably have to install stock rom and then transfer the files and try again.
Hope this helps
Can someone give me a reason of why CM11 is needed to install the CM12?
alexhdkn said:
Can someone give me a reason of why CM11 is needed to install the CM12?
Click to expand...
Click to collapse
Don't know the technical reason but if you try and install CM12 directly from stock ROM it causes boot loops for some reason. If you, however, try and install CM 12 after a complete CM 11 boot, it installs perfectly
Hi, I'm having another weird issue, and is that titanium doesn't restore my games, but the weird thing is that all other apps restores successfully. Any clue?
Enviado desde mi XT1060 mediante Tapatalk
Everything works great but I am getting an error message saying "No SIM card" when there most certainly is a working SIM card. Help.
Edit: I guess this is a problem exclusive to Sprint users. Still, any suggestions on how to get rid of the error message?
rskyline said:
Hi, I'm having another weird issue, and is that titanium doesn't restore my games, but the weird thing is that all other apps restores successfully. Any clue?
Enviado desde mi XT1060 mediante Tapatalk
Click to expand...
Click to collapse
Well, maybe the titanium backup is corrupted/incomplete? Or it is possible that the games aren't compatible with ART yet. Maybe sure that the games you are trying to restore are ART compatible.
Reinstall?
travgyse said:
Everything works great but I am getting an error message saying "No SIM card" when there most certainly is a working SIM card. Help.
Edit: I guess this is a problem exclusive to Sprint users. Still, any suggestions on how to get rid of the error message?
Click to expand...
Click to collapse
I could be because of Sprint, however, try and reinstall. Maybe its just a glitch? Also, sometime, it just takes some time to recognize the SIM.
I have installed twrp 2.8.5.0 on my xt1052 because I didn't know that it wouldnt work. Can I now just flash the 2.6.3.1 version over it using fastboot ? If not, how can I downgrade to a previous version of twrp? Thanks
jellybean411 said:
Well, maybe the titanium backup is corrupted/incomplete? Or it is possible that the games aren't compatible with ART yet. Maybe sure that the games you are trying to restore are ART compatible.
Click to expand...
Click to collapse
Backups are OK. They're coming from my old nexus 4 with lollipop and they get restored correctly on this one on KK. Both games I'm trying to restore are ART compatible, crossy road and kritika.
Enviado desde mi XT1060 mediante Tapatalk
CM11 not available
jellybean411 said:
3. For CM 12 to work, we will first have to install CM 11 and complete a first boot. Follow the following instructions to flash CM 11 first:
A. Download CM 11 ROM for MOTO X (Ghost)
B. Transfer to SD Card and Boot into TWRP recovery [Make sure it is v2.6.3.1]
C. Head into Wipe and Factory Reset your Phone
D. Wipe Cache and Dalvik Cache
E. Then head into install and install the CM 11 zip file (No need to flash GAPPs yet).
F. Once done, perform one complete reboot
Click to expand...
Click to collapse
None of the CM11 nightlies are available from the downloads page. Can you help??
Saibal12 said:
None of the CM11 nightlies are available from the downloads page. Can you help??
Click to expand...
Click to collapse
refer to this post:
http://forum.xda-developers.com/showpost.php?p=58874672&postcount=817
i've just followed this and succesfully flashed AICP from stock 4.4.4.4.4.4.4.4.4.4.4
sursha said:
I have installed twrp 2.8.5.0 on my xt1052 because I didn't know that it wouldnt work. Can I now just flash the 2.6.3.1 version over it using fastboot ? If not, how can I downgrade to a previous version of twrp? Thanks
Click to expand...
Click to collapse
Yes. Just use ADB to flash 2.6.3.1 on top of 2.8.5.0
Saibal12 said:
None of the CM11 nightlies are available from the downloads page. Can you help??
Click to expand...
Click to collapse
Ah. Yes. Forgot about that. Just use any CM 11 based ROM available for Moto X (Ghost).
rskyline said:
Backups are OK. They're coming from my old nexus 4 with lollipop and they get restored correctly on this one on KK. Both games I'm trying to restore are ART compatible, crossy road and kritika.
Enviado desde mi XT1060 mediante Tapatalk
Click to expand...
Click to collapse
This is weird. I don't use Titanium BCKUPS myself so, I wouldn't know. Can you try and download the games from the AppStore and then separated extract your game data from the titanium backups and move them to your phone via file manager?
jellybean411 said:
This is weird. I don't use Titanium BCKUPS myself so, I wouldn't know. Can you try and download the games from the AppStore and then separated extract your game data from the titanium backups and move them to your phone via file manager?
Click to expand...
Click to collapse
Very weird. And no I can't do that because backups are compressed by the app itself. Do you know how to read logs? I have one that might help.
Enviado desde mi XT1060 mediante Tapatalk
rskyline said:
Very weird. And no I can't do that because backups are compressed by the app itself. Do you know how to read logs? I have one that might help.
Enviado desde mi XT1060 mediante Tapatalk
Click to expand...
Click to collapse
Well, it depends on the format type of the log file. Generally most logs are .txt files that can be easily read using Notepad on Windows or TextEdit on Mac.
jellybean411 said:
Well, it depends on the format type of the log file. Generally most logs are .txt files that can be easily read using Notepad on Windows or TextEdit on Mac.
Click to expand...
Click to collapse
I mean to interpret it, I think every person can read it but a few knows what it means. And that's what I want!
Enviado desde mi XT1060 mediante Tapatalk
rskyline said:
I mean to interpret it, I think every person can read it but a few knows what it means. And that's what I want!
Enviado desde mi XT1060 mediante Tapatalk
Click to expand...
Click to collapse
Please do post it. I can't guarantee that I would be able to read it, but I can sure as hell try. I've also got a friend who might be able to help.
Related
Hey there,
Since Lollipop is out and most of you are Rooting it, There's a chance you might run into a BootLoop after flashing the SuperSU through TWRP/CWM. And when this happens, New users mostly flash their Stock Firmware and Restart the process all over again. This is not necessary and can be avoided by following these steps:
RECOVER FROM BOOTLOOP CAUSED BY SUPERSU:
Re-Boot into Recovery mode (TWRP/PhilZ) by Holding the Power and Volume Down button
Select Wipe > Advanced Wipe > Check only Dalvik Cache & Cache
Swipe to Clear the Dalvik Cache and Cache
Re-Boot! (Can take ~6-7mins)
Done!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
CREDITS:
Tip @ joel-n1 posted here.
Click to expand...
Click to collapse
Hope this helps! Thanks
KrishnaSagar said:
Hey there,
Since Lollipop is out and most of you are Rooting it, There's a chance you might run into a BootLoop after flashing the SuperSU through TWRP/CWM. And when this happens, New users mostly flash their Stock Firmware and Restart the process all over again. This is not necessary and can be avoided by following these steps:
RECOVER FROM BOOTLOOP CAUSED BY SUPERSU:
CREDITS:
Hope this helps! Thanks
Click to expand...
Click to collapse
Excellent PSA! I followed your instructions and this seems to have solved my bootloop problems. XT1063 with 5.0 22.21.16.
Thanks man! I rooted it before and had to restore the backup. I'll try now that I'm armed with this info
UPDATE: Can confirm that the method is working. I rooted the phone and the phone went into a boot loop. Cleared dalvik and cache, and voila! the phone booted up.
mahendru1992 said:
Thanks man! I rooted it before and had to restore the backup. I'll try now that I'm armed with this info
UPDATE: Can confirm that the method is working. I rooted the phone and the phone went into a boot loop. Cleared dalvik and cache, and voila! the phone booted up.
Click to expand...
Click to collapse
Glad to help I had my fair share of Bootloops and dont want them to happen again. I can now confidently flash any supersu beta without fear.
Yes..to erase cache, saves alot of flashing..lol
Anytime the device is "stuck" in a bootloop, or stalls on the "unlocked bootloader" screen, power down, boot to recovery, then erase cache..saves me 90% of the time..
sent by my:
Lollipop 5.0_22.11.6 (w/Root)
TWRP v2.8.0.1-titan
UPDATE-SuperSU-v2.16
XT1064 Moto G (2nd Gen.)
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Will doing this delete my data in my phone?
wiping cache&dalvikCache is not working, my phone will boot, optimize apps and works fro like 5 seconds and then it reboots and its stuck back on logo bootloop
help?
ZeroGoCZ said:
wiping cache&dalvikCache is not working, my phone will boot, optimize apps and works fro like 5 seconds and then it reboots and its stuck back on logo bootloop
help?
Click to expand...
Click to collapse
In this case you should flash the firmware again.
Wolfcity said:
In this case you should flash the firmware again.
Click to expand...
Click to collapse
Okay, but how do I root my phone then? What is causing the bootloops?
ZeroGoCZ said:
Okay, but how do I root my phone then? What is causing the bootloops?
Click to expand...
Click to collapse
I suspect you've used the wrong superSU version. What firmware are you on and how did you root the first time? Did you use systemless root? What's the number of the superSU version?
Sent from my Moto G 2014 using XDA-Developers mobile app
Wolfcity said:
I suspect you've used the wrong superSU version. What firmware are you on and how did you root the first time? Did you use systemless root? What's the number of the superSU version?
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
My phone is Leagoo Alfa 1 running lollipop 5.1, stock rom and kernel, twrp v3.0, unlocked bootloader. Tried to flash supersu 2.46, then beta 2.62 and then 2.66. I did not forget to wipe cache+dalvik cache. None of these work. I do not know what systemless root it. (Going to look on it) My last root was on android 4.4.2, so I am new with lollipop.
Edit: This was was never rooted before, I just got it a few days ago.
ZeroGoCZ said:
My phone is Leagoo Alfa 1 running lollipop 5.1, stock rom and kernel, twrp v3.0, unlocked bootloader. Tried to flash supersu 2.46, then beta 2.62 and then 2.66. I did not forget to wipe cache+dalvik cache. None of these work. I do not know what systemless root it. (Going to look on it) My last root was on android 4.4.2, so I am new with lollipop.
Edit: This was was never rooted before, I just got it a few days ago.
Click to expand...
Click to collapse
You know that this is the Motorola Moto G 2014 forum here?
So I dont´t really know what´s the best for your device. Maybe you should have a look in your devices forum (if there is one) or ask in the superSU thread:
http://forum.xda-developers.com/showthread.php?t=1538053
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I had good experience with the BETA-SuperSU-v2.62-3-20151211162651.zip but I´m running a 6.0.1 custom rom.
yeah, I am aware of the fact, that this is moto g 2014, sorry for bothering :|
Anyway, looking at the systemless root - it works on lollipop 5.1.1 and up. Unfortunately my thingy is 5.1 so, no luck there~ *****me*
Thank you for your time and your answer. My posts are mostly ignored...
mali_ said:
Hey! My moto g2 2014 is stuck in logo screen after rooting with supersu 2.78 stable. Which version should I use? I'm unable to root it. Please help.
Click to expand...
Click to collapse
Some more info please. Which revovery? What kind of ROM?
I had sucess on my ROMs flashing BETA-SuperSU-v2.62-3-20151211162651.zip. After flashing you can upgrade it via playstore to 2.78.
Depending on the ROM you´re using you can boot into recovery and reflash it to fix the bootloop.
help bootloop htc one m7
i have an htc one m7,android 5.0.2 and rooted it (CWM-SuperSU-v1.30).then i flash it with BETA-SuperSU-v2.30.
now it cause a bootloop.so i wipe cashe and delvik.but has no effect.
thanks for any help.
I wiped the cache and it's still stuck in the boot loop,I used the latest supersu version and also the latest of twrp
Just use the SuperSU Uninstaller ZIP, wipe your dalvic cache and reboot.^^
Transfer it in TWRP on your internal storage via ADB.
ZIP Download: http://forum.xda-developers.com/attachment.php?attachmentid=3528363&d=1446472307
Hi,,Plz help me.. i am a beginner in rooting.. i have unlocked bootloaded for moto g3, flashed logo.bin to remove warning message,installed twrp , after that i have tried to root using supersu.zip ..Now my phone is stuck in bootloop...What should i do..Plz give suggestion..
i have used below files
twrp-osprey-3.0.2-r1_2
UPDATE-SuperSU-v2.65-20151226141550
logo.bin
all are downloaded from XDa forum itself
i installed Mokee rom60.1 release one on my redmi 2. I enabled root access in developer options but when checked with root checker, it showed not rooted. So, i flashed supersu zip v2.46 thrpugh twrp and wiped cache and dalvik cache.
now i reboot the system but nothing is going on except mokee logo. it is showing more than half an hour. please help me
Reflash everything, before flashing supersu, do it by these steps (taken from here)
1. Don't use the zip method. Download the backup instead and restore it (don't forget to backup your main rom).
2. Download the latest SuperSU zip here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
It must be 2.67+ or higher.
3. In TWRP, go to Advanced>Terminal Command, don't select any folder and type the following commads (you have to clean the textbox in order to type another one):
touch /data/.supersu
echo SYSTEMLESS=true > /data/.supersu
To verify that you made it correctly type
cat /data/.supersu
If you have at hand a desk with adb you can do this quicker using twrp's adb:
touch /data/.supersu && echo SYSTEMLESS=true > /data/.supersu && cat /data/.supersu
If the above commands return
SYSTEMLESS=true
Then it's okay, you can proceed.
3. After that, install the SuperSU zip. It must be the 2.67 version (or higher).
4. Reboot system, if TWRP asks to install root, don't let it and press Reboot System.
UPDATE 10/02/2016- New version of TWRP has been released v3.0.3-0. See below:
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
I have updated versions SM-T800/805 with new builds. TWRP is now v3.0.3-1
TWRP OFFICIAL APP RELEASED: https://twrp.me/app/
Fixes:
Download mode now available in REBOOT options.
Root Shell now available in ADB.
Radio and Recovery backup.
System image backup/restore
Factory image flashing.
Supersu root option removed. This is to pre-empt the upgrade to MM which would cause a bootloop.
MTP fix - MTP now finally working in recovery.
Note: On my PC MTP works perfect in windows 7, but on Windows 8.1 was a little quirky. If you get a USB DEVICE NOT RECOGNISED error after enabling MTP, disable then quickly re-enable MTP and this should fix it.
This version also has system image backup and restore included. It is also possible to flash factory firmware images via the Image install button. (see the TWRP changelog above for more info)
UPDATE 5/3/16:
Have modified the twrp source code and extended factory image partition flashing to include all images except SBOOT.bin (still working on how to flash the bootloader via recovery)
This means BOOT, SYSTEM, RECOVERY, CACHE, HIDDEN, MODEM(RADIO) can all be flashed from the factory firmware. No need for ODIN anymore. As far as I know the Tab S is the only device supporting this at the moment.
(Note: to flash the modem it is necessary to rename MODEM.bin to MODEM.bin.img first)
TWRP_3.0.2-1-T700
TWRP-3.0.2-1-T705
TWRP-3.0.2-1-T800
NOTE: Certain models of the T800 version have a bug at the moment where the screen will be blank when booting to TWRP recovery until the screen timeout kicks in. After that pressing any button will show the screen. As a work around setting the timeout to 15 secs will shorten the wait.
TWRP-3.0.2-1-T805/T807(ATT or Verizon not supported)
twrp_3.0.3-1_sm-t800_10217
twrp_3.0.3-1_sm-t805_10217
FLASH WITH ODIN OR FLASHFIRE OR EXTRACT THE RECOVERY.IMG AND FLASH WITH TWRP
NOTE: It is important to boot to recovery after flashing with Odin or twrp may not stick and will be replaced with stock recovery.
When flashing uncheck auto reboot in Odin, immediately after flashing manually reboot and boot into twrp.
Manual reboot is POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FEEDBACK IS APPRECIATED PLEASE
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
gcappa said:
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
Click to expand...
Click to collapse
As long the bootloader is unlocked, and if someone has an stock recovery pulled from it, then he could be twrp for it
Bootloader is unlocked. But I already flashed a modified cwm which doesn't work too well. So not sure if I could pull the stock recovery unless I reflash the stock rom.
gcappa said:
Bootloader is unlocked. But I already flashed a modified cwm which doesn't work too well. So not sure if I could pull the stock recovery unless I reflash the stock rom.
Click to expand...
Click to collapse
If you have the firmware downloaded just right click on the md5 and open it with 7zip or Winrar, then simply just drag the recover IMG to your desktop and send it here(or link to download). I'm not going to go to much in depth as I don't want this thread to be filled with non related to twrp stuff. I'm also unsure if he has time but ash is one good recovery builder
Ok, I'll do all that when I get home and upload a link.
gcappa said:
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
Click to expand...
Click to collapse
Should be possible as long as the right files are available. This is a snapdragon 805 device?
Seeing as I don't have this device you would have to test the builds and I would need some info from the device. Might take a few builds to get a proper working one.
I take it you are currently rooted? Also could you send me a link to the version of cwm you are using?
gcappa said:
Ok, I'll do all that when I get home and upload a link.
Click to expand...
Click to collapse
Is the sm-n9100 the Chinese version Note 4 Duos?
The TWRP recovery below is for this version, please test:
twrp-2860-n1900
Stock Recovery:
Stock-recovery-n1900
Note: You take responsibility for testing this.
Failed to flash on my T-800.
dwarfer66 said:
Failed to flash on my T-800.
Click to expand...
Click to collapse
What failed to flash? It's made for the t800. It flashes fine on a t805. No one else has had any issues. What is the full version of your device?
ashyx said:
Unofficial version of the latest TWRP, don't think it's been released yet.
Found it by accident for another device, so have rebuilt it for the Tab S Exynos version only.
TWRP-2.8.6.1
Click to expand...
Click to collapse
Thank again ashy this is awesome, keep up the good work.
Confirmed its working T800 5.0.2
ashyx said:
What failed to flash? It's made for the t800. It flashes fine on a t805. No one else has had any issues. What is the full version of your device?
Click to expand...
Click to collapse
This unofficial TWRP fails to flash, just says failed when trying to install.
dwarfer66 said:
This unofficial TWRP fails to flash, just says failed when trying to install.
Click to expand...
Click to collapse
Again, you need to confirm what your exact model is and build number. As you can see from the post above it flashes fine on a T800.
Post a screenshot of the issue with Odin.
It's flashing for me ok on my T800 with IronRom 2.0. Only thing is the root ain't working. Or do I need to unselect auto-reboot and do a forced shutdown? And clear cache and reboot?
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
edit: reflashed IronRom 2.0 to fix cache issue. After the cache wipe it boots up
edit2: it appears to be rooted but it ain't working. But when an app should ask for root permissions the app goes black screen. For Titanium backup it just hangs on checking
RDDraco said:
It's flashing for me ok on my T800 with IronRom 2.0. Only thing is the root ain't working. Or do I need to unselect auto-reboot and do a forced shutdown? And clear cache and reboot?
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
edit: reflashed IronRom 2.0 to fix cache issue. After the cache wipe it boots up
edit2: it appears to be rooted but it ain't working. But when an app should ask for root permissions the app goes black screen. For Titanium backup it just hangs on checking
Click to expand...
Click to collapse
Did you update the supersu app as requested? You need to post a screenshot of root validator so I can see the status of root.
You may just need to select full unroot from settings in the supersu app then boot into twrp and run the root process again or flash the supersu2.46 zip.
Also regarding wiping cache, it can sometimes take longer depending on what's in cache at the time. It may seem like it's hung but eventually completes. On occasion I've seen it take up to a few minutes to wipe.
Just saying that root is broken on custom roms such as iron rom. It's an known issue with touchwiz lollipop roms.
-DUHA
So it's a Rom issue?
What's the actual problem?
Isn't the Rom already rooted, unusual for a custom Rom to not be prerooted?
Guess that explains why it wasn't working. (Tkkg1994 managed to get IronRom working with root in v2.0.5) so its fine for me now.
RDDraco said:
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
Click to expand...
Click to collapse
Looked into this issue and have fixed it. Wipe Cache should work now.
ashyx said:
Unofficial version of the latest TWRP, don't think it's been released yet.
Found it by accident for another device, so have rebuilt it for the Tab S Exynos version only.
TWRP-2.8.6.1
NOTE: If after using TWRP to root you don't see the notification to update Supersu, just install the latest Supersu app from Play. Check root status with Root Validator
Supersu
Root validator
Click to expand...
Click to collapse
Just today, I rooted my new Tab S (SM-T800) AFTER allowing it to OTA update to Android 5.0.2. After that, I used Odin to flash the latest version of CWM I could find for this device, and that trashed recovery altogether. Couldn't get into recovery at all. So I used Odin again to flash TWRP 2.8.6.0 and had recovery back, BUT I kept getting notifications that SuperSU needed to be updated. What I did then was flash "BETA-SuperSU-v2.48.zip", and that resolved the "update needed" problem, and all seems to be working smoothly now. :good:
I'm running stock Touchwiz Lollipop 5.0.2 . Haven't tried changing ROM's, but don't really have a desire to do that just yet.
Alright.
I had this problem for a while and I figured out how to flash the update without the need to factory reset or change the update script of the update file.
Even if you get the user/release-keys error message. EXAMPLE:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You have to be using the latest lollipop release before updating. That means you have to be on YOG7DAS2K1 before attempting.
This worked out for me. But it might not work for you. I do not believe it can destroy your phone and switch some satellites off, but still, not responsible if it did so.
Requirments:
You have to have TWRP now or you at least have ROOT and any flashing app like flashify.
Download COS 13 update file. here https://www.androidfilehost.com/?fid=24459283995316311
Download the latest CyanogenMod Recovery https://download.cyanogenmod.org/?device=bacon
Download the cm-12.1-YOG7DAS2K1 full ROM [url]https://www.androidfilehost.com/?fid=24369303960686198[/URL]
Guide:
Make sure the update cyanogen recovery option is checked in developer options.
Flash CyanogenMod Recovery downloaded before.
Reboot into it.
Use the update function in CyanogenMod Recovery and choose cm-12.1-YOG7DAS2K1 as the update file. It might take a while.
Now reboot to your phone. When booted and running, reboot to recovery.
Now you are running COS recovery. Update with the incremental.
That is it.
I hope this works out for you.
EXTRA: How to ROOT and have TWRP as a recovery:
Requirements:
A laptop.
Download TWRP and adb drivers on the laptop and the SuperSU and TWRP on your phone
Download Oneplus One TWRP Recovery [url]https://dl.twrp.me/bacon/twrp-3.0.2-0-bacon.img.html[/URL]
Get any adb divers. This one suffice [url]http://forum.xda-developers.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339[/URL]
Download the latest SuperSu [url]https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip[/URL]
Guide:
Reboot into bootloader: you can do this in many ways. A simple google search will show you how. Easiest way is to turn the phone off and hold the volume up and power long enough for the phone to boot into bootloader.
Connect your phone to your laptop
Run the adb: I assume you are using windows of course. First put the TWRP .img file in this folder. Hold shift and right click in the folder downloaded above. A 'Open command window here' option will be there. Click it and write in the window
Code:
fastboot boot twrp-3.0.2-0-bacon.img
. A hint: you can just write twrp and hit TAB, it will complete the filename. Or you can rename the downloaded file to just twrp.img
Check your phone, you will be running TWRP temporarily. You now have the option to ROOT only by flashing the SuperSU file downloaded on your phone. If you reboot now you will lose TWRP and get back to the official COS Recovery. If you want TWRP for good flash the TWRP file downloaded on your phone before.
I hope this is easy. It actually is. just follow it step by step.
If you could provide us the guide to root and come back to twrp I would be extremely happy
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
fastboot flash latest twrp and flash SuperSU BETA
THANK the post if I deserve
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
if you need a guide to root, this means you are not rooted, and if you are not rooted most probably you already have stock recovery, which means you can just install the OTA update without any issues.
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
Added as requested. I hope you find it easy.
y2kkingboy said:
Added as requested. I hope you find it easy.
Click to expand...
Click to collapse
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
bisio971 said:
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
Click to expand...
Click to collapse
Yeah. I mad a mistake there. Thank you and glad it helped.
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
thinleytsering9 said:
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
Click to expand...
Click to collapse
As I stated before you have to be on COS 12.1 YOG7DAS2K1. This method should not format your phone or remove any data as there is no factory reset step.
As for the link they are all over the place now. I used the official one. I'll link it for your convenience.
can anyone please pull the stock recovery from COS 13, not 12. I kinda screwed up while updating and now stuck in bootloop.
Update: The issue is resolved. The issue was because of SuperSu 2.46. Installing the latest TWRP and SuperSu 2.66 fixed it. Marshmallow is now rooted!
Thank you very much! After going back to stock and still not receiving the update for more than a week (well at least it felt like a week, Lol) I decided to flash a full COS 13 zip floating around. Instantly liked the new ROM but it had root/symlink issues only to be resolved when flashing a custom kernel it seems. Not what I really wanted so then I stumbled onto your thread and this technique worked 100%! I was on DAS2K1 (flashed thru a custom recovery) already and had several failed attempts flashing just the incremental outright (thru stock recovery)., but by flashing DAS2K1 thru stock recovery first as you suggest then the incremental seems to do the trick.
I did it all the steps, but my phone doesn't not start. After optimizing aplications I have bootloop at "cyanogen modready".
L.E. I think the problem was one of old aplications. After a clean install everything works.
This is the best thing Oneplus one i ever experience.COS13 give my Oneplus one a new breathe of life .This update better than crap lolipop.No Bug for me until now,only google play service need to update twice in play store,its auto reboot itself twice and wholla,super speed UX.The best thing i ever have.I apply update from CM-12-0-YNG1TAS17L Build LRX22G using this method and it works flawlessly
I don't need to factory reset or wipe cache .
I flash full stock ROM cm-12.1-YOG7DAS2K1 and apply update through CyanogenMod Recovery only and nothing else.
Now my oneplus one is rooted and TWRP install using ADB and its fly.All rooted apps is working together with Adaway.
Thanks Cyanogen team for make this 2 years old flagship killer a beast .
Only thing not satisfied is gone signal and wifi status (connectivity indicator ).I need to swipe down to see my transfer data working (what a bummer ).
Thanks so much for this magical guide (y2kkingboy) Yours truly Oneplus one diehard fan.
I was already on cm-12.1-YOG7DAS2K1, however rooted. So even if I had been offered the OTA it would have failed.
Your guide got me updated, first time with no problems.
6.0.1 is such an improvement on 5.1.1, I tried a couple of other 6.0 roms, however this has by far been the most stable and bug free.
Cheers for the tutorial!
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
#sychrome# said:
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
InsaneNutter said:
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2522762
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
I had tried this before and it did not work for me. Kept getting an error saying "the signature file was not a complete file" and therefore it didn't flash. But it may have been editing error on my part. This method works just fine and no need to give up your data either.
Having tried many other ways, I got it done with this instruction.
Thank you!
marxu said:
Having tried many other ways, I got it done with this instruction.
Thank you!
Click to expand...
Click to collapse
Glad I helped.
How to flash cm13 with fp scanner version (both official/unofficial)
Requirements:
- TWRP Alka (Download here, just extract the .img and flash it via your current TWRP )
1. BACKUP!BACKUP!BACKUP!!
Before Flashing anything to your device, we need to backup our full ROM. This can be done by using the TWRP Alka i gave you. steps are in the following:
- Boot Into TWRP
- Go to Backup
- check all the partitions you have (see below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- backup all and wait until its finished (approx 5-10 mins)
For safety purpose store the backup in sdcard or have a copy of it in your PC
2. FLASHING
CAUTION! THIS WILL RELOCK YOUR BOOTLOADER ( Irrespective of if you unlocked officially or unofficially in stock ROM it will get locked and flashing this ROM won't brick your phone or cause bootloops) TWRP will still continue to function normally with all its functions
okay now that we have already backed up all our partitions, we can flash the rom.
- go back to TWRP Main screen (suggesting that you didnt reboot after backing up) and chose Wipe
- Wipe system, Dalvik, Cache, Data
- after its done, go back to TWRP main screen.
- Install the ROM
- Install GAPPS (6.0.1 arm64)
- Reboot.
First boot takes around 5 minutes and it'll initially welcome you in the setup screen.
3. RE-UNLOCKING
Now you know that your Bootloader got relocked. But that's fine, even at a LOCKED state, your TWRP is still functioning as it should be (flashing, restoring, backup, wipe).
So its up to you if you want to unlock or not. Both options are fine and wont affect you in any way.
To unlock your bootloader you have to:
- Boot into Fastboot
- Reunlock Using MiUnlockTool
- reboot.
4. RESTORING to MIUI lollipop or older cm13 builds
if you encounter problems with the rom (stuffs doesnt work, something FC, not a daily use worthy) you can easily go back to where you were before flashing this build.
- Boot into TWRP
- Tap Restore
- check all the partitions and restore
- wait until it finished and reboot.
you should now be in your previous rom (whether its MIUI or AOSP or CM) and the bootloader should've stayed unlock.
Reserved
reserved
Thanks for the tuto. Can we flash miui roms without flashing patched boot.img or else with this recovery ?
the next updates of CM lock bootloader or one-time?
Enviado desde mi XRN3P.
Great tutorial!
One question, I converted my SD to be internal (big mistake). Is there a way for twrp to see the SD and back stuff there?
Or otherwise revert back to external without losing all the data?
Sent from my Redmi Note 3 using Tapatalk
Great! I wanna install this asap!!!
Enviado desde mi Redmi Note 3 mediante Tapatalk
ASAP, for sure! Thanks for your work, Santosh!
There's no emmc-backup in the list in twrp, I flashed the twrp mentioned in op, what's wrong?
Edit: Here's a screenshot, there are a lot things to backup, but no emmc
https://app.box.com/s/mitdohqzvyfql6yf6s3ma8ig24um7ecq
Thank's for guide, working perfect, after full restore I have unlocked bootloader. I had go back to MIUI, there still is no sim card bug for me if in slots is only one SIM and is no trigger to turn off one of them, also camera is working really bad, even colours are bad yelow/black when trying to do a shot.
Sent from my Redmi Note 3 using Tapatalk
Great Job!
Enviado desde mi Redmi Note 3 mediante Tapatalk
Try it or die said:
There's no emmc-backup in the list in twrp, I flashed the twrp mentioned in op, what's wrong?
Edit: Here's a screenshot, there are a lot things to backup, but no emmc
https://app.box.com/s/mitdohqzvyfql6yf6s3ma8ig24um7ecq
Click to expand...
Click to collapse
Facing the same problem. There are a ton of things to backup, yet no EMMC backup. Not sure what's wrong here. Flashed your TWRP via the one I already had and now getting this.
Cristal clear. Eating release to flash. Thanks to dev
Enviado desde mi Redmi Note 3 mediante Tapatalk
nadavar said:
Great tutorial!
One question, I converted my SD to be internal (big mistake). Is there a way for twrp to see the SD and back stuff there?
Or otherwise revert back to external without losing all the data?
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
just go to internal stor-3 dots- migrate data.that would help you.
Sent from my Redmi Note 3 using XDA-Developers mobile app
I am ready to move onto MM. Those who cannot will ask for fix that wont come. So decide. Our dev already gave a detailed instruction. Thanks dev.
Sent from my Redmi Note 3 using XDA-Developers mobile app
same issue[or not an issue],but no emmc ..maybe it is for miui stock and i am on AOSP,..btw flashed twrp and waiting for new update
M.Carter said:
Thanks for the tuto. Can we flash miui roms without flashing patched boot.img or else with this recovery ?
Click to expand...
Click to collapse
I don't know about that but you can't flash any miui lollipop rom after you flash this cm13 and lock your bootloader. You will first have to restore to cm13(older) or aosp with unlocked bootloader and only then you can flash miui.
Or you can also unlock bootloader on the new rom and the flash miui. Correct me if I'm wrong about the last part, Santosh.
Sorry for the messed up (the ss isnt twrp alka, but another recovery) in twrp Alka the emmc backup is aboot and aboot.bak (it has different names for other partitions, but if you backup them all it wont have any problems) ill edit the post rightaway with the proper twrp
Windslash31 said:
Sorry for the messed up (the ss isnt twrp alka, but another recovery) in twrp Alka the emmc backup is aboot and aboot.bak (it has different names for other partitions, but if you backup them all it wont have any problems) ill edit the post rightaway with the proper twrp
Click to expand...
Click to collapse
I flashed mokee ROM (which I know will lock my bootloader) but before that I backup everything using the TWRP alka. And as expected , upon restoring the backup everything is working as they were working before. Bootloader is still unlocked.
the right screenshots are added on the other thread, sorry for the ****ed up
Got understand all steps except 4. How to reunlock the bootloader with mi flash tool. I before unlock bootloader via mi flash tool by flashing full 7.1.8 rom with replace emcc file and then give fastboot command. So now how to reunlock it.
Sent from my kenzo using XDA-Developers mobile app
Red Wolf Recovery Project
Red Wolf Recovery is custom recovery based on the TWRP source code with it's own unique features. And one of these features is also support of the MIUI Incremental OTA's! However this thing is slightly more complicated then just downloading of the zip and flashing.. You have to first enable some things for this and flash some another ZIP file etc. So that's reason why i think that it would be nice to create a guide for this. Now let's look at it...
Pre-requisite
Redmi Note 3 - Snapdragon version!
Common sense
Steps
Download latest build of the recovery from here. And correctly follow the installation process.
After the correct installation reboot your device in to the recovery.
Now click on the "Advanced" and then on "Special Actions".
Here enable these checkboxes:
"Support MIUI Incremental OTA" and "Include System in OTA Survival".
Now clean/dirty flash some full MIUI ROM and flash whatever you want after that.
Now reboot your device in to the system.
When you get some update just download it using updater app and let it automatically reboot in to the RedWolf
Now everything is done! RedWolf will automatically install it and reboot back to the system!
After that you don't have to flash full ROM anymore.. Just always wait for the update from updater app and let it automatically reboot in to the RedWolf.
Now you can flash SuperSU or Magisk and incremental OTA's without any hustles. Use the built-in SuperSU/Magisk option for rooting your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Frequently Asked Questions
Q. I am getting Error 7 while flashing incremental OTA?
Ans: If you are really sure that you followed the installation process correctly then send us a log or screenshot and we will look at it.
Q. Can I install xposed, Viper, blah blah..?
Ans: Yes! You can install anything but make sure that you use this recovery for flashing the zip files.
Q.This recovery can be used in any ROM?
Ans: Yes! You can use this recovery in any ROM.
ATG Droid said:
Red Wolf Recovery Project
Red Wolf Recovery is custom recovery based on the TWRP source code with it's own unique features. And one of these features is also support of the MIUI Incremental OTA's! However this thing is slightly more complicated then just downloading of the zip and flashing.. You have to first enable some things for this and flash some another ZIP file etc. So that's reason why i think that it would be nice to create a guide for this. Now let's look at it...
Pre-requisite
Redmi Note 3 - Snapdragon version!
Common sense
Steps
Download latest build of the recovery from here. And correctly follow the installation process.
After the correct installation reboot your device in to the recovery.
Now click on the "Advanced" and then on "Special Actions".
Here enable these checkboxes:
"Support MIUI Incremental OTA" and "Include System in OTA Survival".
Now clean/dirty flash some full MIUI ROM and flash whatever you want after that.
Now reboot your device in to the system.
When you get some update just download it using updater app and let it automatically reboot in to the RedWolf
Now everything is done! RedWolf will automatically install it and reboot back to the system!
[SIZE="3! You can use this recovery in any ROM.
Click to expand...
Click to collapse
Its much better than ZCX since once zcx is replaced by official twrp then it requires full wipe so keep up the good job.
What is different from zcx twrp
Sent from my Redmi Note 3 using Tapatalk
Androbots said:
Its much better than ZCX since once zcx is replaced by official twrp then it requires full wipe so keep up the good job.
Click to expand...
Click to collapse
Can I flash this on 2gb ram variant?
lordsh said:
What is different from zcx twrp
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Look at the thread in the development section.. Here is the feature list. Anyway the main difference here is that RedWolf is based on the latest TWRP base and it also support AOSP 8.0.0 based ROMs
rohan_45 said:
Can I flash this on 2gb ram variant?
Click to expand...
Click to collapse
Yup
In ZCX the system img file (size more than 1 gb) is stored in sdcard. Do RedWolf also stores the system img file in sdcard ? (for incremental ota updates)
What if i edit build.prop...will i still be able to update incremental updates??
is that really ota update working on it??anyone tested??
umang0712 said:
What if i edit build.prop...will i still be able to update incremental updates??
Click to expand...
Click to collapse
Depends on what will you edit.
I can't save my custom settings, like reverse nav bar, system time etc. It is auto defaulted after every reboot. How can I save them?
Awesome recovery looks great, but I will downgrade to ZCX until the "bad app" checking is fixed.
Thanks.
M RN3 got bootloop . its not booting only mi logo showing what to do pls help fast as it is not my phone !! Its my fathers pls help guys. The device was running miui 8 marshmallow one. I did flashed correctly twrp also boot up but then I selected reboot to system from within twrp and it doesn't boot to system . What to do pls help. No offence to the twrp recovery developer but I need help pls ? Guys
kg hggggg tightly said:
M RN3 got bootloop . its not booting only mi logo showing what to do pls help fast as it is not my phone !! Its my fathers pls help guys. The device was running miui 8 marshmallow one. I did flashed correctly twrp also boot up but then I selected reboot to system from within twrp and it doesn't boot to system . What to do pls help. No offence to the twrp recovery developer but I need help pls ? Guys
Click to expand...
Click to collapse
Dude I got the same problem, download lazyflasher zip file ,flash it through twrp ,and reboot,it worked for me
dudemathai said:
Dude I got the same problem, download lazyflasher zip file ,flash it through twrp ,and reboot,it worked for me
Click to expand...
Click to collapse
Ya i understood so that means that if i want to flash custom rom will i need to flash lazyflasher whenever i flash a custom rom?
kg hggggg tightly said:
Ya i understood so that means that if i want to flash custom rom will i need to flash lazyflasher whenever i flash a custom rom?
Click to expand...
Click to collapse
I don't think you need to flash it when you change roms,what I know is that lazyflasher bypasses miui so that you won't be stuck in bootloop while you flash anything into miui
otyg said:
Awesome recovery looks great, but I will downgrade to ZCX until the "bad app" checking is fixed.
Thanks.
Click to expand...
Click to collapse
What problem are you facing? This recovery seems better and updated than ZCX.
Sent from my Redmi Note 3
can i use magisk with this?
rs168 said:
can i use magisk with this?
Click to expand...
Click to collapse
Yes
is this support with newest miui 9..?
xerocracker said:
is this support with newest miui 9..?
Click to expand...
Click to collapse
Yes
Sent from my Redmi Note 3 using XDA Labs