yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] Foxweed:
Thanks for your reply. :3

It might have been because I granted TWRP access to modify the system. :x I was flashing stock, doing factory reset, then flashing TWRP. From the TWRP file manager, there would always be a /supersu folder BEFORE I was able to sideload the SuperSU beta; I thought it might have been interfering somehow. Eventually I got around it by just temporarily loading TWRP with "fastboot boot twrp-3.0.0-1-manta.img" and not granting it access to modify the system.

S'all good now, anyway. :j
[Nexus 10 Original Android Development] mj56gt:
My N10 with stock 5.1 previously had root with TWRP 2.8.5, but for some reason it recently lost root. In addition, it seems that TWRP has been corrupted because whenever I try to boot into recovery I get a dead bootloader with a red exclamation mart. After I flashed the most recent version of TWRP 3.0.0-1 using "fastboot flash recovery twrp-3.0.0-1-manta.img" (bootloader still unlocked), I still get a dead bootloader when booting into recovery.

How to fix the problem? Thanks!
[Nexus 10 Original Android Development] damngood98:
can't say i've ever run into this but i suppose i'd try downloading and flashing the last stock img from google...if you can get it back to stock 100% you might be okay from there...otherwise, i'm not sure. what procedure did you use to unlock the bootloader? maybe locking that and then unlocking again? if you find out what works let us know, might help others in the future
[Nexus 10 Original Android Development] mj56gt:
Thanks for suggestions!

It turns out that my N10 for some reason does not like those newer versions of TWRP. Once I flashed an older version 2.8.5.0, everything is back to normal. I have no idea why this happened since I have stock 5.1.
[Nexus 10 Original Android Development] metallbloodxox:
Help please my n10 is boitloader unlocked and the method I used flashed twrp 3.0.0.0 but when I flash a ROM cm13 and open gapps 6.0 it boots back to twrp. I tried to flash twrp3.0.0.1 but it didn't boot to it. It keeps booting to twrp 3.0.0.0 . I have also tried to root via adb and shows the red android and the boots to twrp. Can anybody suggest any advise his to get cm13 to boot it keeod going back to twrp. (I used the W droid method tool kit.)
[Nexus 10 Original Android Development] drewski_1:
not sure, but i'm using Khaon's unofficial TWRP (for F2FS support), OmniROM, and [MENTION=4577448]Khaon[/MENTION] kernel

his F2FS compatible TWRP can be found here. maybe it will help?

https://drive.google.com/drive/u/0/folders/0B9kxrJw-dzUmcC03RUZsWXB5bTg
[Nexus 10 Original Android Development] aheeejd:
This is crazy, I flashed twrp (latest) using image flash from previous twrp & now it only boots to download mode. Wtf. Last time I did this same thing happened, but that was my fault, cause I used flashify. This is getting quite ridiculous. Got dl from twrp official. This blows................

Flash through Wugs again. Back up.
[Nexus 10 Original Android Development] drewski_1:
ok, i've been doing the android thing since the OG Droid, but will plead ignorance . . . what's download mode? is that another term for the bootloader screen? or something else entirely.

is this when you try and enter Recovery or when you're just trying to boot to your System?
[Nexus 10 Original Android Development] DocteurN:
I have the same problem... (and same on my Nexus 6P but not on a OnePlus One or Galaxy S3).

No other choice that update through fastboot via a PC :(
[Nexus 10 Original Android Development] Fif_:
Issues with SELinux starting with TWRP 3.0.0-1.

I already have opened a github issue about that problem but wanted to let the XDA community be aware of it.

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/638

3.0.0-0 is functioning fine as far as SELinux is concerned, but the latest 3.0.2-0 is also broken.

See the github issue for the gory details.
[Nexus 10 Original Android Development] marios46:
I have wiped my device nexus 10 with cm13. I tried to restore from a backup I have made with the twrp 3 but I could restore only the system. I saw inside the folder that there is 3 files with data:

data.ext4.win001 data.ext4.win002 data.ext4.win003 (I think that it was happened due to the size).

Did anyone know what I have to do to restore my data? I tried to make a single file with 7z but it says at the log of twrp:

extracttarfork() process ended with error 255
[Nexus 10 Original Android Development] Fif_:
The data.ext4.winXXX files are perfectly normal and expected for large data partitions.

Further mucking with your backup files is unlikely to help.

Do you have a recovery.log file to share instead?
[Nexus 10 Original Android Development] lepa71:
3.0.2-0 has problem installing OMNI 6 with dirty flash and preserving gapps. just FYI.

3.0.0-0 works just fine.
[Nexus 10 Original Android Development] Fif_:
What happens when you try to dirty flash Omni 6 with TWRP 3.0.2?

Recovery.log or it didn't happen [emoji6]
[Nexus 10 Original Android Development] lepa71:
I know it's really hard to believe :rolleyes:

It flashes fine with no error, but Gapps FC. btw it does not happen with 3.0.0-0
[Nexus 10 Original Android Development] three west:
Unfortunately I just discovered the same thing
[Nexus 10 Original Android Development] Fif_:
Well, I was saying in post #657 in this thread that 3.0.2-0 and 3.0.0-1 were having SELinux issues. 3.0.1-0 is likely to have the same problems but I didn't check it.

http://xdaforums.com/showthread.php?p=66217389

Scanno had rebuilt 3.0.2-0 and there's a link here in this post http://xdaforums.com/showthread.php?p=66364970 with a working 3.0.2-0 manta TWRP build.
[Nexus 10 Original Android Development] schell0385:
New girl on the block flashing TWRP

Hello everyone.

Most of this is new to me. Some information I have read I understand, but the real techno stuff I get a bit lost.

I have Manta 5.1.1 rooted. Before I tried any of this I backed up my device with Titanium Pro to Google drive.

FYI: I have researched everything I could find and read 54 pages of this block without finding my answers. So I thought it time I ask the big boys and girls for their professional assistance.

I was using the TWRP Manager app, when I realized I wanted the real TWRP. I read before I could download TWRP 3.0.2-0, I needd to install an earlier version. I installed v2.8.4.0. So far so good. I copied the image for v3.0.2-0 to my device using TWRP v2, used File Explorer to find my new image, flashed it.

This is wear things get confusing. The flash took. I wiped what I was suppose to.....eventually I wiped EVERYthing (after 8 attempts). When I boot into Recovery I have v3.0.2-0. When I boot into the System I have v2.8.4.0.

I just booted back into recovery and TWRP v3.0.2-0 shows up on the screen that says, "Unmodified System Partition" and swipe to allow modifications.

I have done this over and over. I am hoping someone here can tell me what I am doing wrong.

My other option would be to restore my Titanium backup, and try installing TWRP some other way.

Two more questions question: after fixing TWRP, can I restore my backup to get my apps back?

Now would be a good time to install a custom ROM that is STABLE, and I can do fun things with. I have read many reviews. Is there a custom ROM that is fun, stable and would upgrade my nexus to marshmellow or nougat - and have all my features work. I need my camera.

Thank you,

LoriAnn - the new girl
[Nexus 10 Original Android Development] mr.natural:
- just uninstall the twrp app should do the trick. (Meaning you can only use twrp in recovery mode)

- yes you can restore your apps

- if you want a very stable ROM, stick to KitKat. And forget about Nougat as the camera is not working on any of them ATM.
[Nexus 10 Original Android Development] schell0385:
Fixed it...not sure how

------------------------

Yes....I was always in recovery mode. TWRP would switch back and forth between versions. Now I am wondering if I could have two versions in my internal memory. I am going into file explorer to see if I can see anything.

Is it possible to have two versions of TWRP in internal memory......would it be on the SD Card portion or in the System partition? I will explore and see what I can find.

Isn't KitKat very old? I had Manta.....which I liked but I wanted to try flashing a custom ROM. I flashed aosp with khaon kernel..........

but i will put this in another thread.

ANYWAY, after I flashed the ROM - when I go into recovery I have TWRP v.3

Thank you for replying!!
[Nexus 10 Original Android Development] ilciumbia:
Probably you have inadvertently flashed the old recovery in system partition... No big deal, flashing a good rom from TWRP 3.0.2.0 will straighten things up.

A very good MM ROM I am using now as my daily driver is Resurrection Remix 5.7.4 compiled by Corinna. Fast, stable, everything working. I do not recommend Kahon's kernel unless you plan to use f2fs (which I don't recommend either, really no point to it), because it does not have Low Memory Killer, and after a while things do get very slow to the point you have to reboot.

My recommendation again goes to RR, see thread in development section.

Inviato dal mio Nexus 10 utilizzando Tapatalk
[Nexus 10 Original Android Development] linsalata28:
I just got one of these and unlocked the bootloader then rooted and flashed the latest TWRP. I'm having a issue with making backups. It's just not making them. It said it was backing up and completed but when I look on the internal memory there is no TWRP folder with a backup. There is a file only named TWRP and says 0b. Should I roll back to 3.0.1?

Thanks for any replies.
[Nexus 10 Original Android Development] drewski_1:
are u looking in TWRP, or in OS
[Nexus 10 Original Android Development] Fif_:
I've seen that happen sometimes: check /data/media/TWRP (as root or booted under TWRP).

Sometimes, TWRP puts its directory there instead of /data/media/0/TWRP.

I've never found out why :)

If that's the case, it's okay to move the directory to its right location and symlink the bad location.
[Nexus 10 Original Android Development] linsalata28:
Thank you. It was under "data/media/0"

I've never seen that before but at least I know know.
[Nexus 10 Original Android Development] DowntownRDB:
Has anybody tried to do a restore with TWRP 3.1 yet? 3.1 installed without issue and made a back-up without issue. However, when attempting to restore using 3.1 it is taking a long, long time. Previous version of TWRP did not take this long. Also, experiencing the same long time for restore on my Nexus 9. So just curious if it is just me or others also.
[Nexus 10 Original Android Development] DowntownRDB:
EDIT: Not sure why initial restore was taking so long. It appears to now be working without issue and as fast as previous version on restore.
[Nexus 10 Original Android Development] andi2398:
Hey Guys,

i have a problem with TWRP. I´m on the latest twrp version. When i try to make a backup, it´s starts normally and after about 30% of the data partion following error appears: createTarFork() process ended with signal: 9. I also attached a screenshot.

Anyone knows this error? I searched in google and xda, but there are no really help :-/

greetings

Andi
[Nexus 10 Original Android Development] rogers11:
Hello, I've wiped the system partition today. After that, flashing the latest LineageOS 13.0 with TWRP 3.1.0 failed with error 7. After downgrading to TWRP 3.0.2 from within 3.1.0 I was able to install the system. :confused:
[Nexus 10 Original Android Development] Nikola Jovanovic:
What are advantages of enabling rm -rf instead of formatting ? Thanks
[Nexus 10 Original Android Development] drewski_1:
Can be significantly faster.
[Nexus 10 Original Android Development] goodflood:
There are reports of TWRP 3.3.0-0 failing on devices. My manta got bricked, when I tried to use the TWRP install method. See more of my ticket on github here: https://github.com/TeamWin/Team-Win-...ct/issues/1446. So be aware!

Anyone know what I can do to get back to TWRP twrp-3.2.3-0-manta.img or get back into system? ADB devices does not show anything.

EDIT:

So, after researching the TWRP MANTA forum, I share the frustration of user: aheeejd...

<FRUSTRATION> "WTF and this blows" (and a few other four letter words of my own : ) </FRUSTRATION>

PROBLEM: https://xdaforums.com/showpost.php?p=66195748&postcount=653

He was able to fix it using WUGS Toolkit

WUGS TOOLKIT: https://xdaforums.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452

which asks to flash an older MANTA recovery

SOLUTION: https://xdaforums.com/showpost.php?p=65352407&postcount=643

which I did; then, I updated the TWRP to latest working and flashed [MENTION=5480152]followmsi[/MENTION] latest manta ROM

https://xdaforums.com/nexus-10/development/rom-lineage-14-1-20170216-unofficial-t3557735

So, this has happened at least once before in 2016... [not trying to piss anyone off]. I will be careful next time~!
[Nexus 10 Original Android Development] cobalt100b:
Had the same problem with my Nexus 10 as the user directly above this post:

Fashed TWRP from 3.2.1 or so to 3.3.1 on my Nexus 10 with the official TWRP-App. Downloaded the Image File as well with this App.

Result was a soft brick. At least I think that's the right term. Tablet startet only to the little green Android robot with the Options Start/Power Off/ Recovery Mode/Restart Bootloader.

Could neither start the normal System nor the Recovery Mode any more. I had to reinstall a Stock ROM with the Nexus Root Toolkit and got it running again after some additional problems. Recovery Mode is still not accessible any more. So I will reinstall TWRP 3.2.3.

Any idea what went wrong?

Is there after all any reason to prefer the new 3.3.1 Version over the older ones like the 3.2.1?
[Nexus 10 Original Android Development] buxtor:
Can't flash TWRP

I've had this tablet for a month now on stock and finally got around to rooting and romming it. I got the Bootloader unlocked with Wug's toolkit, but it hangs at the TEMPORARILY BOOTING TWRP portion. I found another guy who hadn't charged his on XDA so I charged it and tried again. I get to the same step with no booting to TWRP. I've tried flashing other versions of TWRP with the toolkit to no avail. I'm wondering if the Recovery partition has become compromised, as I tried reformatting it through the toolkit. No joy, Goose! Also not sure if it matters, but when flashing TWRP by letting the toolkit download it, I get a mismatch error.

Please advise!

:confused:
[Nexus 10 Original Android Development] rudolf895:
I know this reply is like a year fxing late lol but can you twrp from try

twrp-3.2.3-0-manta-parted-fdisk.static.img

drive.google.com
[Nexus 10 Original Android Development] alias_neo:
Same issue for me,

Two different usb sticks, 1.3GB data partition giving 1.9GB backup size, first attempt errored after half an hour or so, second completed successfully after ~9000 seconds. (150 minutes). Far too long.
[Nexus 10 Original Android Development] rlrbjr:
I agree the internal memory speed is great. But after creating the backup to internal memory; the copy from internal memory to the USB stick only took a couple minutes. There seems to be something else causing the problem.
[Nexus 10 Original Android Development] Matthileo:
Is there any way to prevent TWRP from including the Google Music cache in a /data backup? I have 10ish GB pinned to my device, and it makes doing a backup impossible.

[sent from my nexus 10]
[Nexus 10 Original Android Development] dreadlord369:
After reading all of the posts, I can't figure out whether or not you need to unlock your bootloader in order to install this. I am rooted but the bootloader Is still locked. Anyone know?
[Nexus 10 Original Android Development] dboftlp:
I only know fastboot oem unlock my friend ;)
[Nexus 10 Original Android Development] scott_doyland:
In the latest version of TWRP for the nexus 4/7/10

(note that /sdcard is really /data/media in Android 4.x)

1. TWRP option to factory reset does NOT wipe /data/media (where photos etc are stored)

It does wipe /data (where apps are installed).

A factory reset from within the stock ROM does wipe /data/media and /data and leaves just /system (ROM) intact.

I would say that is a bit confusing to the end user as a factory reset can mean different things in this case.

2. TWRP option to wipe internal storage ONLY wipes /data/media (this will include all sub directories inc multiuser subdirs).

3. TWRP option to 'format data' wipes/formats /data and /data/media (so it ends up like it would after a stock ROM factory reset)

4. TWRP option to wipe system ONLY wipes /system (ie the actual ROM).

I would guess if anyone has had TWRP wipte /data/media when chosing the TWRP factory reset option then its maybe a bug at an older level.

The above is all much better explained in the links provided by an earlier posters, ie

http://teamw.in/whattowipe

http://teamw.in/DataMedia
[Nexus 10 Original Android Development] nick w:
This is by far the best recovery i have ever uses.

THANKS!

#Now on my N10 and GNex
[Nexus 10 Original Android Development] scott_doyland:
I didnt mean to give the impression that I have anything to do with TWRP (apart from using it). I was just trying to clear up some misunderstandings earlier in the thread.
[Nexus 10 Original Android Development] newellj79:
Yes you do.
[Nexus 10 Original Android Development] dreadlord369:
Alright cool, thanks for the heads up.
[Nexus 10 Original Android Development] ShadowVlican:
um... no you don't

my bootloader is locked and i've got TWRP (thanks to goomanager)

i'd show you a video for proof, but the serial number is right there
[Nexus 10 Original Android Development] NovaFox238:
-_-

SCRATCH THIS POST >< fixed... *facepalm*
[Nexus 10 Original Android Development] scott_doyland:
Hi,

Don't you need to be root to flash a recovery if the bootloader is locked ?

How do you gain root without an unlocked bootloader ?

To be honest I see no reason to not unlock the boot loader anyway as widely this makes life easier :)
[Nexus 10 Original Android Development] doumer:
hm, somehow i allways get a bootloop when I install TWRP (latest version) via fastboot =(

EDIT: nevermind, sorry. just did a factory reset from within twrp and its booting again =D
[Nexus 10 Original Android Development] htowngator:
So I just wiped cache, data, dalvik, and system.... twrp erased my entire storage. I know what I'm doing and this is not normal.
[Nexus 10 Original Android Development] sam3000:
It's perfectly normal on a device that puts internal media storage in /data/media like the nexus 10.

Read the scott_doyland post on the previous page for more info.

You should just use factory reset if you want to safely wipe without deleting media.
[Nexus 10 Original Android Development] htowngator:
That's ridiculous if so and the TWRP people need to modify the recovery in that regard. Either remove it or change the verbiage.
[Nexus 10 Original Android Development] OLYMPIAKOI:
:cool:

Is this TWRP compatible with the Nexus 7?:confused:
[Nexus 10 Original Android Development] scott_doyland:
Google twrp and you can find the latest official twrp for your device on the twrp website.

Wasn't too hard to find was it :)
[Nexus 10 Original Android Development] NeverAlwaysEver:
When this recovery starts, its asking me to enter the password and what do I enter as password? I didn't set any password on the tablet also. It seems I can't do factory reset without this password.
[Nexus 10 Original Android Development] biggboii:
Could you guys please add the Verizon Galaxy Note II to your project? (If you haven't already) This would be much appreciated. Thanks for all your great work!
[Nexus 10 Original Android Development] wptski:
TWRP has OTG support. I use StickMount to mount a flash drive which works fine from TWRP. GooManager can start TWRP, I assume that the mount be lost? Or can either app be modified to retain the mount so one can backup from GooManager directly to a flash drive?

It's all about if the backup function from Goo Manager into TWRP is a automatic function or does it just boot into TWRP and one can still mount a flash drive, etc.?
[Nexus 10 Original Android Development] tvBilly:
I'm not sure I understand your post exactly, but I think it's (essentially) the same one I was about to ask.

Is there any way for me to backup from TWRP to an external thumb drive plugged in via an OTG adapter. The adapter (and the exFAT formatted thumb drive) work 100% with the current version of StickMountPro when I'm booted and running in standard (but rooted) JB 4.2.1, but I can't select "external SD" as a backup destination when in recovery (TWRP 2.3.2.3).

Hmmm, just posting this made me think that maybe my problem is that the thumb drive is formatted exFAT. When I get home I'll try it with a standard FAT32 formatted thumb drive (and post if that turns out to be what my problem is).

Edit: That was it for me. TWRP is backing up to my thumb drive just fine as I type. It doesn't work to an exFAT formatted thumb drive, but it does to a FAT32 formatted thumb drive. When the backup is finished, I'll try a NTFS formatted thumb drive to see it that works. wptski: is your thumb drive formatted FAT32?

Edit 2: And it doesn't work with an NTFS formatted thumb drive either. So it looks like FAT32 only (though maybe one of the ext linux formats will work too).
[Nexus 10 Original Android Development] wptski:
It's FAT32.

Maybe I can phrase it differently. If you have a external SD Card slot, you can mount it in TWRP and every time you boot into it the setting is retained not so with OTG support. I haven't tried the "backup" function from Goo Manager to see if OTG mount is retained. If you boot into recovery(TWRP) from Goo Manager, it doesn't.

I haven't installed a ROM from GM but I did install a Gapps(BTW, it installed the wrong one) and the operation was automatic. If the "backup" function is automatic also, this is where I wonder where it will store the backup?
[Nexus 10 Original Android Development] GadgetCheck:
Original Development Should stay at its rightful place :D
[Nexus 10 Original Android Development] Slig06:
Hi,

Last night i got a hang&reboot bug, then it failed to boot... all wipe and factory reset was not sufficient, only a format data finally allow me to boot again, loosing all my "internal sd" datas :crying:

- would it be possible to add a fsck function ? (can't be sure a fsck on data partition would have saved it, btw i would have preferred tried it before format)

- what about a way to backup/restore the internal sd datas (without backuping the whole data partition) ?
[Nexus 10 Original Android Development] wptski:
Someone posted this in another thread. Go to the Stickmont app page, click on "MORE" in the description, scroll down and there are a couple of links to a file to put in your root folder that'll allow R/W on NTFS formatt.

I just connected my docking station with a 750GB HD formatted with NTFS to my N10 and was able to R/W to it. Didn't try any video streaming, etc. just a simple text file. How cool is that?
[Nexus 10 Original Android Development] tvBilly:
It was me that posted in the other thread. :)

Two slightly different things we're talking about here. StickMount works fine with NTFS and exFAT formatted volumes when you add the two suggested files to the root of your internal "SD Card". This only works when you're already booted though. In this thread, I was talking about being able to read/write from recovery (TWRP) to an external USB stick, for the purpose of making a nandroid backup directly to the stick (or restoring directly from a stick); that will only work to a FAT32 formatted USB stick, as the two suggested files on the (internal) SD card aren't accessed when in recovery mode.
[Nexus 10 Original Android Development] wptski:
I see what you meant now.

You don't happen to have Stickmount Pro do you? I emailed the Dev asking what more it does, no reply? I emailed the Dev of Goo Manager about issues, no reply either!