Develop Bugs

DISCUSSION: YU Yureka CM 12(S) Lollipop Update

Current firmware: Android 5.0.2, Build LRX22G, Cyanogen OS version 12.0-YNG1TAS0W0
OTA: http://builds.cyngn.com/cyanogen-os...deeca328/cm-12.0-YNG1TAS0W0-tomato-signed.zip
Fastboot flashable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Boot Debuggable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-boot-debuggable.img
Use OTA for manually update from any official KitKat build; don't use fastboot flashable images on existing devices with KitKat bootloader - it will brick the device!
How to unbrick: http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040 (Credit goes to @tirta.agung)

OTA downloaded.... Now going with flashboot...

Need Some Help
Deleted

anyone flashed it yet???
Sent from my AO5510 using Tapatalk

Flashed it..initial boot will take a long time

blackyz said:
OTA downloaded.... Now going with flashboot...
Click to expand...
Click to collapse
I tried fastboot method now my phone is not booting

anyone done it successfully? my DL is halfway so I need procedural help.

Phone not booting
sharan.nyn said:
I tried fastboot method now my phone is not booting
Click to expand...
Click to collapse
I flashed with fastboot process successful but my phone not booting, nothing happening. i don't know what to do now no logo just dead.

I flashed it with TWRP.
Awsm CM12S.
Super smooth !

mralam92 said:
I flashed with fastboot process successful but my phone not booting, nothing happening. i don't know what to do now no logo just dead.
Click to expand...
Click to collapse
Same here bro!
now following this
http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040

sharan.nyn said:
Same here bro!
now following this
http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
Click to expand...
Click to collapse
service centre help or not?

Posted cm12
Just installed the zip version of cm12 on yu. Could not wait for the official ota update. Updated zip using cwm recovery which I had installed while the phone was running on the cm11 kitkat 4.4.4 version.
I understand that since this is just a system update there is no need to change or revert back to the original recovery.
(just a doubt- is it necessary to revert back to original 4.4.4 system stock recovery in case we get the OTA or the OTA will take care of any Custom recovery and will install iteslf?)
Initial boot will take a long time due to the Android Runtime (ART) virtual machine which is the improvisation over the Dalvik Cache. So please be patient for all the 122 apps to get registered in by ART. I had tried the ART while on cm11 4.4.4 (despite of system warning that it might lead to crashes etc... ), even then it took a very long time......
Working absolutely fine. Initial experience is awesome. Will be observing it now for some time. Most other features are similar to the cm11. no more 3g detection errors. Got to explore more....
My first posting in XDA.
I owe a lot to this community from which I have taken a lot. I hope I will be able to give back even little that I have got to help others. :good::good:
By zip version i mean the version that can be installed using the phone recovery with out the need of a computer to push the system (i.e. the flashable version). I am not aware what the debuggable version means.

mralam92 said:
service centre help or not?
Click to expand...
Click to collapse
Service center said they will pickup the device in 7-8 days

please tell me difference between OTA,Fastboot flashable image and Boot Debuggable image.And which one should I download to install.?

Titokhan said:
OTA: http://builds.cyngn.com/cyanogen-os...deeca328/cm-12.0-YNG1TAS0W0-tomato-signed.zip
Fastboot flashable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Boot Debuggable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-boot-debuggable.img
Click to expand...
Click to collapse
Is the Android version 5.0.x or 5.1?
Has anyone encountered any bugs at all?
To flash through recovery, do I need the OTA version?

CM 12 update
guys plzzz help me as lollipop is out for yu...can i install ?? i have rooted my yu but i m still on stock rom i.e cm 11 and i have cwm ,can i flash the cm12 zip file using cwm ..

dont flash thru fastboot all who flashed it thru are having hard bricked devices

weshall said:
guys plzzz help me as lollipop is out for yu...can i install ?? i have rooted my yu but i m still on stock rom i.e cm 11 and i have cwm ,can i flash the cm12 zip file using cwm ..
Click to expand...
Click to collapse
YES YOU CAN JUST FOLLOW THIS STEPS
1. Download official CM12s Ota(1st zip in the link).
2. Place the downloaded zip file in the ‘download’ folder on phone’s internal storage.
3. Boot Yureka into Stock Cyanogen recovery - To do so, power off the phone. Then press Volume Up + Volume Down and Power button simultaneously,Onec you boot into recovery do data/ factory reset.
4. Select ‘Apply Update’ > ‘choose from internal storage’ > /0 > Download > and select “cm-12.0-YNG1TAS0W0-tomato-signed.zip” file. The ROM will be flashed and you should be seeing the Android Bot
5. Once installation is over, go to main page and ‘wipe cache partition’
6. Then select Reboot system now
That’s it! Wait for a while as the device boots for the first time with all new and fresh Cyanogen OS 12.
IF you dont get anyhting just revert me back ,or pm will help you.:laugh:

Titokhan said:
Current firmware: Android 5.0.2, Build LRX22G, Cyanogen OS version 12.0-YNG1TAS0W0
OTA: http://builds.cyngn.com/cyanogen-os...deeca328/cm-12.0-YNG1TAS0W0-tomato-signed.zip
Fastboot flashable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Boot Debuggable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-boot-debuggable.img
Use OTA for manually update from any KitKat build; don't use fastboot flashable images on existing devices with KitKat bootloader - it'll brick the device!
Click to expand...
Click to collapse
It just got updated if you flash it on kitkat bootloader, the device will get bricked
Many users have got their device bricked, the warning was too late I flashed it today at 1:50 AM

weshall said:
guys plzzz help me as lollipop is out for yu...can i install ?? i have rooted my yu but i m still on stock rom i.e cm 11 and i have cwm ,can i flash the cm12 zip file using cwm ..
Click to expand...
Click to collapse
Hi, You can very well install the .....signed.zip using the CWM recovery as I did.
1. Install the .....signed.zip file and not the ....flashable.zip or the ....bootable.zip files. Only the .....SIGNED.ZIP file either on your phone memory or sdcard
2. Reboot into the recovery mode either by using the advanced reboot option or by pressing the volumeup+down button and power buttons simultaneously and releasing them once you see the Yu logo and phone vibrates.
2. Use the Factory reset command first and then wipe the Cache
3. Navigate to the Install zip and chose the .....SIGNED.zip from either your phone memory or the SD Card as CWM has the option to chose the zip file. and swipe to install it.
4. After successful installation navigate to reboot and swipe to allow the system to restart.
5. Intial boot takes a very long time saying Android is updating. This is because Lollipop uses Android Runtime (ART) by default and not Dalvik Cache as a virtual machine for all apps. So please be patient till all the 122 or so apks are updated by ART. Takes around 10-15minutes.
6. The usual fist time boot stuff.... and then...
7. Enjoy. CM12 it is sweet.
---------- Post added at 09:58 AM ---------- Previous post was at 09:43 AM ----------
id74em8 said:
Is the Android version 5.0.x or 5.1?
Has anyone encountered any bugs at all?
To flash through recovery, do I need the OTA version?
Click to expand...
Click to collapse
It is android version 5.0.2
To flash through recovery (either CWM or TWRP) use the .....SIGNED.ZIP i.e. the first file in the list and NOT the .flashable.zip or the last one. Only the first one.
I installed the zip through CWM
The only bug I noticed was when you add the Powersaver option tile in the Notification drawer, when in the power saving mode, a notification showing the power save mode got invoked. When I used the same option after rebooting I am not getting it now..
Also all of a sudden a red boundary started to appear at the edges of the screen. So I though I had opted for the screen refresh notification in the Developer options but I had not. Still i could see the red rectangle when the screen refreshed. I had to reboot the system. Now fine.

SM-T800 on Marshmallow 6.0.1 - How do you root or install TWRP on this?

I was previously on cm12.0 but wanted to get back to stock for 6.0.1. Got back to stock but now I can't stand the bloat. Has anyone rooted the stock 6.0.1 yet?

jawz101 said:
I was previously on cm12.0 but wanted to get back to stock for 6.0.1. Got back to stock but now I can't stand the bloat. Has anyone rooted the stock 6.0.1 yet?
Click to expand...
Click to collapse
Just flash TWRP with Odin then flash the supersu zip through TWRP.

Thanks. I got through it all. It's been a while since I've rooted this tablet. My Linux laptop and Virtualbox eventually played nice. Also, apparently any old cord doesn't work. I had to use the original Samsung USB cable for Download Mode to work.

Root SM-T800 6.0.1 with TWRP
paulshriner said:
Just flash TWRP with Odin then flash the supersu zip through TWRP.
Click to expand...
Click to collapse
Thanks for the heads-up..
As I've never used TWRP before (always rooted with Chainefire''s CF-Auto-Root still not available for SM-T800 6.0.1), could you please post a quick step-by-step on how to root the new Marshmallow 6.0.1 on a SM-T800.
Much appreciated..

terrord8158 said:
Thanks for the heads-up..
As I've never used TWRP before (always rooted with Chainefire''s CF-Auto-Root still not available for SM-T800 6.0.1), could you please post a quick step-by-step on how to root the new Marshmallow 6.0.1 on a SM-T800.
Much appreciated..
Click to expand...
Click to collapse
This link is not for our tablets but is the same process. Just make sure you find the correct TWRP version for the T800. Once you have TWRP installed find Supersu and copy it to your tablet's SD card. Use TWRP to install Supersu. http://www.cyanogenmods.org/forums/topic/install-twrp-recovery-samsung-android-using-odin/
Sent from my SM-T800 using XDA-Developers mobile app

I'm also on MM 6.0.1 having just bought this device. I'd like to install this rom:
https://forum.xda-developers.com/galaxy-tab-s/development/rom-android-6-marshmallow-tab-s-10-5-lte-t3219759
So how do I go about it please? Do I need to unlock the bootloader?
:edit: Followed the guide and got TWRP installed. Downloaded the Gapps (very slow download), SuperSu zip and Nougat rom from here. Did a wipe of dalvik, cache, data and system. Sorted. Only problem is I bought the tablet for reading comics and for some reason my comic reading apps can't "see" the cbr files on the micro SD.

So I have tried re downloading Odin and Twrp and flashing it. It passes Everytime. But when I boot to recovery with power home and vol up. It goes to Android recovery. Any tips solutions you could help me with? Thanks very much in advance

After flashing twrp in odin did you reboot to recovery ? Pretty sure u need to reboot to recovery to get it to "stick",
Otherwise I believe your tab will change it back to origanal recovery
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.

I had the same problem and I solved it by chance by finding a post online. It seems that after you flash TWRP with Odin it is indeed properly installed but you can't access it because when you boot into recovery it boots into Samsung's recovery. To get to TWRP you need to do the following:
1. Power off your Galaxy Tab S 10.5. Wait 6-7 seconds after screen goes off.
2. Press and hold the three buttons Power + Home + Volume down together until you see warning screen.
3. Press Volume Up to continue to download mode.
4. Reboot again pressing POWER + HOME +VOL DOWN but as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons and wait.
5. Voila TWRP!
I hope it worked for you as it did for me.

Yes
paulshriner said:
Just flash TWRP with Odin then flash the supersu zip through TWRP.
Click to expand...
Click to collapse
I did root the. samsung galaxy sm-t800. watch my vldeo.
https://youtu.be/Ih2IifEUq84

LG G4 keeps booting in recovery mode (TWRP)

Hi,
I made a CM14 update yesterday, but since then, my phone boots in recovery mode. I tried to reinstall TWRP, in current and previous versions, and other roms (I can flash), but nothing works; each time I reboot, TWRP appears...
Any hint ?
Thanks very Much !

gdoucou said:
Hi,
I made a CM14 update yesterday, but since then, my phone boots in recovery mode. I tried to reinstall TWRP, in current and previous versions, and other roms (I can flash), but nothing works; each time I reboot, TWRP appears...
Any hint ?
Thanks very Much !
Click to expand...
Click to collapse
Try to install my latest BETA (check my signature)

steadfasterX said:
Try to install my latest BETA (check my signature)[/QUOT
Hi, thanks for your answer. I tried, but it still reboots on TWRP... (tried to install AICP).
There's an error message when installing :
patching system image unconditionnally
E:unknown command [log]
But it keeps going on with "dectected filesystem ext4 for /dev/boot [...]
Then it reboots in recovery...
Click to expand...
Click to collapse

gdoucou said:
steadfasterX said:
Try to install my latest BETA (check my signature)[/QUOT
Hi, thanks for your answer. I tried, but it still reboots on TWRP... (tried to install AICP).
There's an error message when installing :
patching system image unconditionnally
E:unknown command [log]
But it keeps going on with "dectected filesystem ext4 for /dev/boot [...]
Then it reboots in recovery...
Click to expand...
Click to collapse
Please try build 186
Click to expand...
Click to collapse

dont work for me same Probleme

TooThPicK said:
dont work for me same Probleme
Click to expand...
Click to collapse
Try my latest beta and if that is not working build 186
And which nightly causes that problem?

i think its not the recovery i test the cyanogen and this dont work
test installing stock but dont work
testet both not working
no Rom is working evrytime its boot to recovery

TooThPicK said:
i think its not the recovery i test the cyanogen and this dont work
test installing stock but dont work
testet both not working
no Rom is working evrytime its boot to recovery
Click to expand...
Click to collapse
Which cm version? tell exact build date.
Try to reflash stock kdz

Is there a way to Flash kdz from fastboot or recovery lgup dont find my device
ok i find the download mode now lgup find my device i downloading 20g and test

The issue is due to change in Google code not being compatible with TWRP.
I had the same issue, I flashed stock ROM with LGUP and then flashed CM14.1 after that.
Once your back up and running you can't use the in built updater, you have to download the update, manuay reboot to recovery and then flash.

Lgup dont find my device i only have recovery and fastbood

ceanth said:
The issue is due to change in Google code not being compatible with TWRP.
I had the same issue, I flashed stock ROM with LGUP and then flashed CM14.1 after that.
Once your back up and running you can't use the in built updater, you have to download the update, manuay reboot to recovery and then flash.
Click to expand...
Click to collapse
The change in Google code was the reason for one of the beta series I made. I was able to fix that in twrp even when this is no twrp issue. The internal updater worked fine afterwards when using any build after 15 of dec while using my latest beta.
That's why I ask several times what cm build they used (both do not answered this yet).
This is important so I can reproduce the issue and may can release a new twrp workaround if possible.
.

TooThPicK said:
Lgup dont find my device i only have recovery and fastbood
Click to expand...
Click to collapse
Not sure dude, best to post in the dedicated TWRP or cm14.1 thread.

its fixt thank you for your help the trick is turn off the g4 hold the + button and plugin the cabel now the device comes to downloadmode and now lgup is working
---------- Post added at 02:30 PM ---------- Previous post was at 02:28 PM ----------
steadfasterX said:
That's why I ask several times what cm build they used (both do not answered this yet).
This is important so I can reproduce the issue and may can release a new twrp workaround if possible.
.
Click to expand...
Click to collapse
on my is the nigtly from 23.12

I got the same problem booting permanently in TWRP.
Flashing the build (02.12.) I had before also doesn't work.
Some kind of tips here?

xXfreshXx said:
I got the same problem booting permanently in TWRP.
Flashing the build (02.12.) I had before also doesn't work.
Some kind of tips here?
Click to expand...
Click to collapse
Install my latest beta. I know that this do not solve the problem but then after flashing it try to boot into system. This will fail. Then pull the recovery log and provide it on http://paste.omnirom.org
If you don't know how to get that log it is easy. Check my FAQ #4 A.
http://forum.xda-developers.com/showpost.php?p=68249027&postcount=3
.

steadfasterX said:
Install my latest beta. I know that this do not solve the problem but then after flashing it try to boot into system. This will fail. Then pull the recovery log and provide it on http://paste.omnirom.org
.
Click to expand...
Click to collapse
Thanks for your reply
https://paste.omnirom.org/view/6e5948df

xXfreshXx said:
Thanks for your reply
https://paste.omnirom.org/view/6e5948df
Click to expand...
Click to collapse
Hm . This is really after a boot into system??...
Ok as I cannot see relevant data pls do the same again but with build 186 now. Provide the log again. The reason is that this build handles the bootloader commands in an other way and I may see then what I wanna see.
Thx
.

Hm . This is really after a boot into system??...
Ok as I cannot see relevant data pls do the same again but with build 186 now. Provide the log again. The reason is that this build handles the bootloader commands in an other way and I may see then what I wanna see.
Thx
.
Click to expand...
Click to collapse
Here you are.
https://paste.omnirom.org/view/594df4ce

xXfreshXx said:
Here you are.
https://paste.omnirom.org/view/594df4ce
Click to expand...
Click to collapse
Hm the reason for that reboot lays somewhere else...
Please tell me exactly what you had done to produce that loop:
Which exact version of cm installed before upgrading?
Upgraded with internal cm updater or by flashing new zip in twrp?
The above would help me to reproduce the issue.
Besides the short questions above it would be great if you could test 2 things for me and if not skip to 3 (if you're in hurry):
1. The hw key combo test
2. The force twrp test
3. Last resort LG up
1. The hw key combo test
Flash the latest beta twrp and reboot into this twrp
Create a full backup if not already done so!!!
Power off the device and pull out the battery
Use the hardware key combo to get into factory reset screen (press vol down + power and keep them pressed. plugin battery. Wait until you see the LG logo and then release only the power button for 1 sec then press it again and keep both pressed until you see the factory reset screen)
Follow through this process and twrp will showing up without resetting anything
Grab the recovery log and paste it again
Then try to reboot to system
2. The force twrp test
If the first method hasn't worked it would be great to see the log anyways but then try the the following:
Boot into twrp (doesn't matter how for this test)
Flash again the latest twrp beta with twrp itself (choose img button at the bottom) and now when getting asked flash it to BOOT partition! Yes this is no problem or causes any damages. Just do it.
Then choose reboot into system and twrp will popup again (but now it starts from boot partition)
Now install the cm version of your choice or any other rom
Do NOT reboot yet
before rebooting grab the recovery log again and paste it again
3. LG up
If the above does not work and as I believe you need your device back soon the best bet would be do a full backup with the latest twrp beta version. Then use LG up to flash stock kdz again to get a working device.
.

[Unofficial] [Updated 021217] TWRP 3.2.0-0 Mi Note 2 Themes & Aroma Guide

Unofficial TWRP 3.2.0-0 Mi Note 2 (scorpio)
Unofficial TWRP build for the Mi Note 2.
TWRP 3.1.1-0 Changelog https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
Compatible with TWRP Backup and Recuse Tool for PC
Download Link
twrp-3.2.0-0-scorpio.img
Update 14/07/17
Update TWRP to 3.2.0.0
Update 14/07/17
Update TWRP to 3.1.1-0
New streamlined kernel
Add F2FS support
Improved Android 7.0 Miui compatibility - If issues persist please let me know
Update 30/05/17
All features working as expected
Screenbrightness adjustment is now responding accurately with a suitable default brightness
Updated kernel.
Much quicker booting.
Installation Guide
Once you've got you're bootloader unlocked with MiFlash and run through all the Xiaomi hoops to unlock your bootloader and have a fastboot installed on your PC:
Simply place the download where you like and then open a command prompt and type
fastboot flash recovery /path/to/twrp-3.1.1-0-scorpio.img
BONUS THEMES & File Manager
Plus as a special treat I'm including a full guide below to use Materialised Theme and Aroma File Manager both working within TWRP 3.1.1-0
Themes available from here
1. Install the latest TWRP linked above.
2. Download one of the themes above (see screenshots below for recommendations)
3. Download Aroma File Manager for TWRP from here
4. Once booted into TWRP select Install and choose the theme.zip you've downloaded.
5. You will instantly see the theme applied
6. Click Install again and this time select "materialised_aromafm_200-b7.zip"
7. Once that zip has completed installing open the Materialised Options (the art palette icon on the top right)
8. Tick the box that says "Use Aroma File Manager"
9. Press back and select "File Manager" from the list.
10. Swipe to start Aroma File Manager
11. Enjoy!!
See attached thumbnails for themes in action.
Source:
https://github.com/stonetrapping/twrp_android_device_scorpio
Special thanks to:
z31s1g for the wonderful themes and the Aroma File Manager

Thanks, dude !

Working OK for both MIUI and AOSP based ROMs?

Working with ASAP and MIUI and encryption all round.

That's great! Thanks for sharing

After flashing this recovery, it boots right back into stock recovery. Any idea what i'm doing wrong? Do I have to disable dm-verity or something?

stephendt0 said:
After flashing this recovery, it boots right back into stock recovery. Any idea what i'm doing wrong? Do I have to disable dm-verity or something?
Click to expand...
Click to collapse
You can keep dm-verity. After flashing I'd suggest leaving fastboot and booting straight into recovery via fingerpress.
Flashing SuperSU or Magisk or similar should ensure survival of TWRP if it's being overwritten.

Works great but I found :
1. Reboot to TWRP is so slowly... Why ?
2. System won't boot into TWRP when wipe everything and reboot to TWRP. I need to turn phone off and then press volume up + power button to enter TWRP again.
Is there any chance to fix those ?

Kris Chen said:
Works great but I found :
1. Reboot to TWRP is so slowly... Why ?
2. System won't boot into TWRP when wipe everything and reboot to TWRP. I need to turn phone off and then press volume up + power button to enter TWRP again.
Is there any chance to fix those ?
Click to expand...
Click to collapse
1. I've noticed the slow speed too, I'm 100% sure why it's happening but I have some ideas.
2. The same ideas will hopefully address this issue.
It was a quick and dirty port since there was no native TWRP, I haven't had the time yet to improve it but I'll build an updated release based on 8.2.5.0 sometime soon and look to making it official.

Kris Chen said:
Works great but I found :
1. Reboot to TWRP is so slowly... Why ?
2. System won't boot into TWRP when wipe everything and reboot to TWRP. I need to turn phone off and then press volume up + power button to enter TWRP again.
Is there any chance to fix those ?
Click to expand...
Click to collapse
Lastest TWRP build
https://mega.nz/#!NBwyjKrK!XELWAAwehtKnXgXOge_y16kEP0Uqscv_5LVx-YqTzcc
Boots quicker. Screen brightness is fully adjustable. Reboot to recovery from TWRP is working
Has been submitted to TeamWin for official status but for now remains unofficial.
Please let me know your thoughts.

Thanks, StoneTrapper !!
I will check later after flashing new version !
StoneTrapper said:
Lastest TWRP build
https://mega.nz/#!NBwyjKrK!XELWAAwehtKnXgXOge_y16kEP0Uqscv_5LVx-YqTzcc
Boots quicker. Screen brightness is fully adjustable. Reboot to recovery from TWRP is working
Has been submitted to TeamWin for official status but for now remains unofficial.
Please let me know your thoughts.
Click to expand...
Click to collapse

Really fast at boot, maybe because is a release from the future (30052017 )
great job, thanks man!

Can not use usb otg function ...
Can not use usb otg function ...
Otg function, no work

[email protected] said:
Can not use usb otg function ...
Otg function, no work
Click to expand...
Click to collapse
I've had no issues with USB-OTB, with any standard formatted flash drive (FAT32, NTFS, EXT4).
This is also the first I've heard of anyone having such an issue.
Does the OTG drive mount successfully in whatever ROM you're using? Is it attached prior to booting to TWRP? Can you provide additional information.
TWRP doesn't like remounting the same USB multiple times - i.e if you unplug the USB while in TWRP, and then reattach the same drive it won't remount it.

Sorry to feedback lately because I was too busy in past 2-week.
Well, new TWRP is working well.
The only one problem: If I want to upgrade firmware, TWRP will be replaced by MIUI stock recovery after flashing new version of MIUI ROM.
It's pretty annoying because I need to get into fastboot mode then flash TWRP. After that, entering TWRP and flash lineage OS ...
Is it possible to be fixed in next coming version ?
Kris

May I know how to flash the TWRP rom?

I'm on MIUI.eu ROM, can I flash full global MIUI original ROM with TWRP without bricking the phone ??
Before on Redmi note 3 u can't flash original ROM without bricking the phone, u needed special TWRP (zxc version) or modify the ROM
Can you explain me ?
Envoyé de mon Mi Note 2 en utilisant Tapatalk

Link down.

chemha said:
Link down.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=673368273298968884
Will op fixed shortly.

StoneTrapper said:
https://www.androidfilehost.com/?fid=673368273298968884
Will op fixed shortly.
Click to expand...
Click to collapse
It does not work. No download link found

Haven't flashed in over 2 years. Missing anything?

I went to the dark side in April 2016, and haven't flashed anything in about 2 years. Wife's tablet (flo) needs an update, MM is getting laggy though the tablet has always been good to us.
Titanium was getting to be crap around the last time I used it, with problems mostly restoring, does that still hold true? Might just use it to back up a couple apps she uses a lot and just use Play Store to restore the rest. It's not really important, just curious.
Downloading the TWRP app, I know TWRP is installed but willing to bet it needs to be updated and the app can do that.
Tablet is near its EOL, not planning on rooting it if the ROM doesn't come pre-rooted. I have no idea what Magisk is.
So I'm gonna go into TWRP, wipe system, wipe data, wipe cache, wipe dalvik. Flash ROM (going with Lineage 15.1). Now at one point 2-3 years ago the common wisdom was starting to become "flash ROM, boot ROM, reboot to recovery and then flash Gapps." Y'all still doing that? Or can I just flash Gapps right after flashing ROM and reboot then?
Bit nervous as I haven't flashed in a while, but also kind of exciting.

We've got Android 8.1 Oreo now... Working perfectly on our Nexus 7... You should check it out...

Any suggestions for which are the most stable roms to try? I'm in the same boat. I'm on android 6.0.1, stopped flashing things a while ago and it might even be official! But mine's running like a dog so think I wanna try something to jazz it up!

You should try pure Nexus rom based on 7.1.2 for ultimate good battery life. Oreo is Good but battery isn't the greatest.

Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING

ganggreen777 said:
Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING
Click to expand...
Click to collapse
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:

k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
Thanks so much for responding back!!!!
Tonight I will follow the steps. I trust it will go fine.
Excited to do this. ......yep I waited this long to root this device

k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
I did the 'install lineageOS on flo and installed TWRP latest. Seem like fastboot went into a slew of commands
and finished. I followed the steps to reboot into recovery and twrp is not there. Android dude opened with red triangle.
I have no clue whats up. I leave it sit, and it reboots into android splash screen and bootsup so i can use the tablet. I guess this is why I am soo perplexed. "Am i missing something?"

ganggreen777 said:
....twrp is not there. Android dude opened with red triangle.
...."Am i missing something?"
Click to expand...
Click to collapse
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html

k23m said:
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html
Click to expand...
Click to collapse
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device

Kevin_McLaughlin said:
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device
Click to expand...
Click to collapse
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.

k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this ordecr or else TWRP will be gone again.
Click to expand...
Click to collapse
Why u asking???? Have we chatted b4?¿?
I will do as stated above (I swear I am (thinking) I am doing it as above all the other times. (when you say copy output...is that from the fastboot dialogue? ) ...is it as easy as copy paste ...I dont remember how to copy via adb fastboot...
(Makes me wonder if twrp is really being fastbooted into the n7 2013
Thanks for helping.

k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.
Click to expand...
Click to collapse
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.

ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs

ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:

beachfl said:
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs
Click to expand...
Click to collapse
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS

ganggreen777 said:
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS
Click to expand...
Click to collapse
BTW
I am great to go.....thanks very much for helping me thru
---------- Post added at 01:06 AM ---------- Previous post was at 01:04 AM ----------
k23m said:
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:
Click to expand...
Click to collapse
BTW I am great to go... Thanks for sticking thru with me