yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Vonnegut:
There is none EFS partition in the One.

Here's the major block mmcblk0 splitted into 29 partitions (and their respective sizes).

major minor #blocks name

179 1 65536 mmcblk0p1

179 2 512 mmcblk0p2

179 3 32 mmcblk0p3

179 4 32 mmcblk0p4

179 5 1024 mmcblk0p5

179 6 500 mmcblk0p6

179 7 16384 mmcblk0p7

179 8 500 mmcblk0p8

179 9 1024 mmcblk0p9

179 10 1536 mmcblk0p10

179 11 1536 mmcblk0p11

179 12 10240 mmcblk0p12

179 13 10240 mmcblk0p13

179 14 1355776 mmcblk0p14

179 15 32768 mmcblk0p15

179 16 524288 mmcblk0p16

179 17 16384 mmcblk0p17

179 18 1536 mmcblk0p18

179 19 1 mmcblk0p19

179 20 8 mmcblk0p20

179 21 1024 mmcblk0p21

179 22 16384 mmcblk0p22

179 23 32768 mmcblk0p23

179 24 32768 mmcblk0p24

179 25 16384 mmcblk0p25

179 26 8192 mmcblk0p26

179 27 65536 mmcblk0p27

179 28 58510540 mmcblk0p28

179 29 294895 mmcblk0p29

These are the partions names and devices names

lrwxrwxrwx root root 1970-02-05 13:00 DDR -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 1970-02-05 13:00 DRIVER -> /dev/block/mmcblk0p23

lrwxrwxrwx root root 1970-02-05 13:00 LOGO -> /dev/block/mmcblk0p22

lrwxrwxrwx root root 1970-02-05 13:00 aboot -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 1970-02-05 13:00 boot -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 1970-02-05 13:00 cache -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 1970-02-05 13:00 dbi -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 1970-02-05 13:00 fsc -> /dev/block/mmcblk0p19

lrwxrwxrwx root root 1970-02-05 13:00 fsg -> /dev/block/mmcblk0p18

lrwxrwxrwx root root 1970-02-05 13:00 grow -> /dev/block/mmcblk0p29

lrwxrwxrwx root root 1970-02-05 13:00 misc -> /dev/block/mmcblk0p21

lrwxrwxrwx root root 1970-02-05 13:00 modem -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 1970-02-05 13:00 modemst1 -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 1970-02-05 13:00 modemst2 -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 1970-02-05 13:00 oppodycnvbk -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 1970-02-05 13:00 oppostanvbk -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 1970-02-05 13:00 pad -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 1970-02-05 13:00 persist -> /dev/block/mmcblk0p15

lrwxrwxrwx root root 1970-02-05 13:00 recovery -> /dev/block/mmcblk0p17

lrwxrwxrwx root root 1970-02-05 13:00 reserve1 -> /dev/block/mmcblk0p24

lrwxrwxrwx root root 1970-02-05 13:00 reserve2 -> /dev/block/mmcblk0p25

lrwxrwxrwx root root 1970-02-05 13:00 reserve3 -> /dev/block/mmcblk0p26

lrwxrwxrwx root root 1970-02-05 13:00 reserve4 -> /dev/block/mmcblk0p27

lrwxrwxrwx root root 1970-02-05 13:00 rpm -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 1970-02-05 13:00 sbl1 -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 1970-02-05 13:00 ssd -> /dev/block/mmcblk0p20

lrwxrwxrwx root root 1970-02-05 13:00 system -> /dev/block/mmcblk0p14

lrwxrwxrwx root root 1970-02-05 13:00 tz -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 1970-02-05 13:00 userdata -> /dev/block/mmcblk0p28

System, persist, cache and userdata are EXT4 type partitions.

Modem is FAT16. All of the others are binaries.
[ONE Original Android Development] playya:
[MENTION=5427631]Vonnegut[/MENTION] not sure what this has to do with me though?
[ONE Original Android Development] Vonnegut:
You already know the answer...do you remember what happened that summer in 1995?

Ok, ok, just a wrong quote :9
[ONE Original Android Development] playya:
Hahaha OK just checking with ya
[ONE Original Android Development] Vonnegut:
So, anyone?

I even tried with linuxreader but to no avail.

Is that top secret? If so, don't kill me please, i have a dog.
[ONE Original Android Development] dictionary:
I think the efs back up is of modemst1 and modemst2
[ONE Original Android Development] Vonnegut:
Guess so.

Anyway i read that it doesn't work...so i did backup everything with ADB myself
[ONE Original Android Development] bud77:
I confirm it's modemst1 & 2

My EFS backup log gave me those 2 partitions (mmcblk0p10 & mmcblk0p11)
[ONE Original Android Development] DuckMcQUack:
How did u do it?? :)
[ONE Original Android Development] PeterGuru:
Re the signature ... thanks!

On everything else, now I'm even more confused.

I've been using CM12 since it came out a couple of weeks ago. The nightlies flash perfectly well each day. However, when I do a Nandroid, which I perform once a day, it appears to be successful because TWRP tells me it's successful. Nonetheless, I tried to restore the latest Nandroid this morning, and I got the loop. I then tried to restore several other Nandroids, all CM12, and all caused the loop. By the way, whenever I restore a Nandroid, I always completely wipe my system (except internal storage), so that the Nandroid can restore on a clean device. In the past, with every other phone I've had, the restore went perfectly well, and it was simple. This time, though, nothing! Just the continual loop from the OnePlus first screen and then back to TWRP.

I've done this 1000s of times, but now I'm at a complete loss as to what's happening. Obviously the Nandroid is NOT successfully re-installing even though I get a SUCCESS notification in TWRP after the restore is complete. It's when I then try to reboot the system when the loops begin.

So, as it stands, it's impossible for me to restore any Nandroid, so what's the use?

I also tried flashing your firmware after the complete wipe and BEFORE the restore process. I also tried flashing your firmware after the restore. Nothing helped. I then tried flashing the latest CM12 nightly, the one that was working prior to this entire mess, and then performing the restore, and the same problem happened. I also tried flashing the latest CM12 nightly AFTER the restore process and, again, the same loop issue. Basically, I've tried everything I can think of, with no success.

Now I've wiped the system, for about the 10th time this morning, and JUST reinstalled the latest CM12 nightly and GAPPS. My phone is back up and running again, but now I have to spend about 4-6 hours to not just re-install all my apps, but to then go into each one and set them up properly. It's a frustrating and pain-staking procedure.

Restoring Nandroids via recovery is really the most important function of any recovery, and it's simply not working with TWRP 2.8.4.1.

Peter
[ONE Original Android Development] DesignGrits:
The latest build is broken, and has been mentioned a few times in this thread. Flash back to the previous build.
[ONE Original Android Development] PeterGuru:
Tried it ... no success.

I tried restoring my Nandroid from yesterday's build, but also no success. Again, I've tried numerous Nandroids from builds over the last several days, all without success.

The Nandroids are simply not restoring.

Peter
[ONE Original Android Development] Lanchon:
if that doesnt work, use titanium backup or nandroid manager to restore your apps directly from the nandroid backup.
[ONE Original Android Development] DesignGrits:
Worked for me. Thats how I got back to the previous build.
[ONE Original Android Development] tobitege:
[MENTION=899563]PeterGuru[/MENTION]: really sorry to hear about all the troubles you had already. I'm using MultiRom which comes with its own recovery and thus I haven't had the "honor" (horror) with 2.8.4.1 like you had.
[ONE Original Android Development] Lanchon:
which one is the one that works?
[ONE Original Android Development] Heisenberg:
This might seem like a stupid question but I have to ask it. When you make a nandroid which partitions do you backup? System? Data? Cache? Boot?

Transmitted via Bacon
[ONE Original Android Development] xanthrax:
Deleted

Sent from my Darkside of 1+1
[ONE Original Android Development] PeterGuru:
Basically ALL Partitions ...

Sorry for the long delay getting back to you. Finding time to visit xda is becoming harder and harder with each passing day.

To answer your question, I backup pretty-much all partitions ... all the ones you noted above.

However, I did find out why I was having problems several days ago, and it had to do with an app called Online Nandroid Backup Pro. Somehow it was not doing a proper Nandroid because, once I got everything up-and-running again, with all apps re-installed, I did a Nandroid from directly within TWRP, and then a full wipe and restore. Everything worked perfectly.

I did not, and will not, install Online Nandroid Backup Pro. I'm now using TWRP Manager to handle backups more easily; however, the one feature not available in TWRP Manager is automated backups via time. Previously, with Online Nandroid Backup Pro, I could set up the app to do a Nandroid at 7am each morning.

Peter
[ONE Original Android Development] ek69:
What are you using that app for? Installing backups, making backups, etc should be done within twrp itself. I don't trust that app much for anything really (from personal experience). I've seen it (and had it) cause way more issues than its worth and it's not an official app made by TWRP either.

Personally I do my backups manually, it's more effort but at least I know if I ever need that backup it's going to work 100% and not have any issues with it. I've learned this the hard way ;)

If you want to flash updated twrp or switch between versions easily, use the app called "flashify", it can install the .IMG files directly without going into twrp to install the zip or fast boot

Cheers :)

Sent From Lollipopified Bacon Goodness!
[ONE Original Android Development] Heisenberg:
I have to agreee with [MENTION=785380]ek69[/MENTION] on this one. Don't trust the TWRP app to do your nandroids for you, or anything for that matter. It's been proven to be pretty unreliable, I've seen countless posts and threads discussing it causes major issues. Take the time to boot into TWRP and do your backups properly. Sure, it takes an extra 60 seconds (at the most), but it's worth it. If you're going to do something, do it right, don't cut corners.
[ONE Original Android Development] theCroh:
I had the exact same problem with Online Nandroid Backup on D802. I've done my backups from the recovery since I realized that.

Lähetetty Nexus seiska 2013:sta Tapatalkilla
[ONE Original Android Development] PeterGuru:
At this point I have to agree with you both. Although I never had an issue with Online Nandroid Backup Pro before, it's clearly not working properly, and I have now begun to do all my Nandroids through TWRP directly in recovery. Yes, it takes longer, but it's worth the trouble.

The ONLY issue I have with doing a Nandroid directly in TWRP recovery is using the automated backup name. I've asked about this feature before in the official TWRP forums, but no response after many months. I wish the automated name would be the CyanogenMod version instead of the Build Number. The Build Number really is useless to me because it doesn't tell me what version of CM has been backed up. Yes, I know ... you don't have to tell me that I can change the name myself, but with a very successful company to run, plus my two very small children to help raise, plus an 85-year-old mother with Alzheimers to help take care of, even an extra minute or so is precious to me.

For example, instead of the following automatically generated name:

2015-01-29--15-34-15 bacon-userdebug 5.0.2 LRX22G ebe6250ecd test/

It would be much better to have:

2015-01-29--15-34-15 12-20150129-NIGHTLY-bacon

However, thank you both for your comments.

Peter
[ONE Original Android Development] tobitege:
[MENTION=899563]PeterGuru[/MENTION]: agree with you on the suggestion to generate a more "readable" name! I, too, always change the name manually, especially since I have 8(!) LP roms on my phone via MultiRom and frequently update them. ;)
[ONE Original Android Development] nabeeleinstein:
Updating the situation, I used MSMtool to hard reset the phone and cleared all partitions. Still the TWRP problem persists. It is not an issue with other recoveries at all.

Also a thing to note is that as soon as TWRP boots, the PC gives a USB not recognised message, the screen is unresponsive to touch and the phone reboots. I tried using an old version which worked fine with KitKat, but the problem persists.

Any ideas?
[ONE Original Android Development] strategist99:
reverted back to the 2.8.3 version because there is a problem with the mtp mode on this latest version.

regards
[ONE Original Android Development] LeroViten:
OMG, it must take you up to long to update and keep them... ;)

I used to maintain two ROMs and got lazy. :P
[ONE Original Android Development] Toobie:
Tried to flash the latest version after the latest OTA update..

Actually rebooting all the time to the cyanogen recovery and unable to flash root :(

What can I do?
[ONE Original Android Development] xanthrax:
Developer options / untick update cm recovery and flash again

Sent from my Darkside of 1+1
[ONE Original Android Development] Toobie:
Thanks man!

I just didn't recognized this button.
[ONE Original Android Development] HansiHusten:
I'm usually not flashing but only booting into TWRP every time I need to root with "fastboot boot xxx2.8.4.1.img" after an OTA.

Unfortunately since the new OTA update for the OPO I cannot boot into the latest version (2.8.4.1) and I have update cm recovery unticked. I dont want to flash so any solution? Tried older versions of TWRP but also no luck.

Shows me all the time the fastboot mode + icon :/
[ONE Original Android Development] knuspertante:
What's the reason for non flashing?!

On my device TWRP (installed) runs great ;)
[ONE Original Android Development] xanthrax:
I don't understand the issue, find a better description Hansi

Sent from my Darkside of 1+1
[ONE Original Android Development] dubazar:
Deleted
[ONE Original Android Development] tobitege:
[MENTION=383605]HansiHusten[/MENTION]: open Settings|Developer options and check if you have an option "Update Cyanogen recovery" and make sure it is unchecked/disabled.

Edit: oops... misread... but if the CM recovery keeps coming back, toggle that option on/off then go into fastboot and flash TWRP again, then reboot into recovery and see if it sticks... weird issue.
[ONE Original Android Development] dubazar:
But normally he should boot in Cyanogen Recovery not in fastboot in all case
[ONE Original Android Development] tobitege:
But if it only fastboots means that the recovery didn't flash correctly in the first place, pending the correct implementation of the rom.
[ONE Original Android Development] xanthrax:
I guess, if that update recovery is ON when flashing only a custom, it will go to fastboot, there's no cm recovery to update if flashing only a custom, it will update it only by flashing the stock ROM because it will erase the recovery, then the command will say, update cm but there is no cm... only that custom which won't be flashed

Sent from my Darkside of 1+1
[ONE Original Android Development] HansiHusten:
To have the original recovery on it to receive OTAs without sideloading

The CM recovery option is 100% disabled and its not coming back on its own :) Tried check/uncheck multiple times, doesnt help

Well after installing the OTA I push latest supersu via ADB on /sdcard/

boot than into fastboot to "fastboot boot *.img" to get TWRP booting and then select zip file to flash supersu - this way everything stays stock and thats the way I prefer after flashing of dozent ROMS etc. and have done it so often in the past..

Now as I mentioned, with the new OTA on my OPO I am not able to boot into TWRP or the good old CWM recovery to flash the zip.

Does this clarify now my problem?

I guess flashing works for the most ppl, but just booting into it doesnt (at least not for me ^^) I will see if I find an other way to apply the supersu.zip without flashing any new recovery.

Or did I miss something? Does the default CM recovery allow zip installation? (edit: No it doesnt)

My usual procedure:

adb push SuperSU-vxxxxx.zip /sdcard/ -> push supersu.zip

adb reboot-bootloader -> boot into fastboot

fastboot boot cwm.img or twrp.img -> send img but BOOT and not flash

flash superzu.zip -> inside cwm or twrp install zip file

done
[ONE Original Android Development] L10nH34Rt:
Just to clarify, you are using the

fastboot boot recovery recovery.img

command and not

fastboot boot recovery.img

right?
[ONE Original Android Development] xanthrax:
You're not able to boot into twrp because you didn't flash it...

Use flashify

Sent from my Darkside of 1+1
[ONE Original Android Development] L10nH34Rt:
From my understanding he wants to boot via fastboot, not by using advanced power menu.

He doesn't need to flash it in this case.
[ONE Original Android Development] xanthrax:
I just don't understand what he wants... Sorry

Sent from my Darkside of 1+1
[ONE Original Android Development] bombadier:
What he is wanting to do is to boot into twrp to flash the superuser zip,he wants to stay with stock recovery for whatever reason and only needs twrp to flash a zip to get root, thing is I did not know that you could still do that on 44S I thought it only worked on earlier versions 25 or 33
[ONE Original Android Development] xanthrax:
And? What's the main problem here? To flash twrp? What's that hard?

Sent from my Darkside of 1+1
[ONE Original Android Development] bombadier:
The only problem is he cannot do it the way he has been doing it, dont understand myself why he will not flash TWRP but thats people for you
[ONE Original Android Development] bombadier:
DONT Download as its a reboot fest

Changelog

What's new in 2.8.5.0:

Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution

Improve thread handling and move input handling into the main rendering thread to improve stability

Make MTP work even if unplugged and plugged back in

Unify scrollable list code and make kinetic scrolling feel more natural

Fix handling of mapped zip files for OTA updates (CM12 updater)

USB keyboards should now work on all devices that support USB host mode via a USB OTG cable

Other small fixes and improvements
[ONE Original Android Development] DesignGrits:
People, don't flash it....TWRP keeps rebooting every time I go into it after flashing this update. Also, once in TWRP none of the buttons work before it reboots.

UPDATE: Flashing again to see if it keeps doing it.
[ONE Original Android Development] HansiHusten:
Well I have always used fastboot boot xxx.img and it always booted into it.

It worked without any issues on 44S

As I said before, I dont want to flash it because I want to receive official OTAs and dont want to sideload

If you check my details im nearly 10 years here on this board and flashed alot more than just android roms or recoveries...

I managed to boot into this version with my usual commands, but I am unable to touch on any button and then it auto reboots after 5 seconds or so :/

----

BUT

never mind, I found my issue.

I used an USB3 port for sending the image file to my OPO.

Now that I used good old USB2 port the older version of TWRP worked fine and I was able to boot into it WITHOUT flashing anything. So if any1 has also the same issues, use USB2 ports and not USB3 :)

Thanks to anyone who tried to help
[ONE Original Android Development] bombadier:
Stay on 2.8.4.1 as 2.8.5.0 is not working same reboot problems as were with 2.8.4.0
[ONE Original Android Development] DesignGrits:
Yep, tried through adb flash and flashy app on the play store, new update does not work.
[ONE Original Android Development] xanthrax:
So, during that push "session" through USB 3, was it any errors showing up in cmd?

Sent from my Darkside of 1+1
[ONE Original Android Development] gianton:
Strange cause 2.8.5.0 working fine on my device, made a backup and flashed a few zips with no issues. Using latest theme from here.

I flashed it with the zip I made (link) as I'm away from my laptop.
[ONE Original Android Development] strategist99:
hi, any fix for the usb mount in enable mtp yet??

pls

regards

---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------

hey@Gianton, uploaded an update..

thanks man, will download and flash away...

this version, you uploaded fixes the MTP enable issues??

regards

---------- Post added at 10:08 PM ---------- Previous post was at 10:07 PM ----------

hey@Gianton, uploaded an update..

thanks man, will download and flash away...

this version, you uploaded fixes the MTP enable issues??

regards
[ONE Original Android Development] bombadier:
Dees_Troy is aware that there is an issue
[ONE Original Android Development] gianton:
Can't test it sorry. But everything else seems to be working fine on my device.
[ONE Original Android Development] bombadier:
2.8.5.1 is up

http://techerrata.com/browse/twrp2/bacon

the .1 is just to fix the problem of it rebooting, there was an error in the build script,have just flashed it and the rebooting problem is fixed, however I cannot get MTP to work in windows but that might just be a driver problem on my computer(However when the roms booted it works fine)

MTP is not working at all in recovery for me, how about anyone else ?
[ONE Original Android Development] Lar5:
Deleted...
[ONE Original Android Development] gianton:
2.8.5.1 flashable zip,

http://www.mediafire.com/download/4js2ck4k9ri46z6/twrp_2.8.5.1-bacon.zip
[ONE Original Android Development] tobitege:
Thank you for your exemplary service, my friend!
[ONE Original Android Development] Spider1996:
I don't want to make a mistake but flashing the Original Image thought TWRP is available so why we need a flashable zip?

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] reaper000:
Convenience, my friend, just pure convenience. Most people here have a custom recovery already in place to flash a zip, while fewer may have Flashify or similar installed.
[ONE Original Android Development] dmarden:
I think he means that TWRP can now flash image files directly.
[ONE Original Android Development] strategist99:
screw it man, still no MTP fix...

nonetheless, thanks for the update.

i am still on 2.8.3.0 version I think as that has a correct MTP..

regards
[ONE Original Android Development] geowolf1000:
mtp working

win 7

open devices from sett

mtp device and one files click

if not mtp device attach update drivers from web

check if you have nexus adb is wrong driver
[ONE Original Android Development] NYZack:
Can anybody fill me in on whether TWRP is now working with encrypted Lollipop systems? The last version didn't seem to be able to decrypt my Lollipop Nexus 7, and I've been holding off on encrypting my OPO until TWRP supports this.
[ONE Original Android Development] paarkhi:
Sorry for off topic but I don't know where to ask so asking here as this is a recovery thread - [MENTION=912474]Dees_Troy[/MENTION], can you please also build the latest version for multirom, it is still stuck at 2.8.4.

Thanks
[ONE Original Android Development] thepaperescape:
I've got a bacon w/ twrp 2.8.5.1 and no installed ROM (don't ask)

I'm ideally trying to adb push latest CM nightly (02/13) and then flash. No big deal right? I'm following http://xdaforums.com/showthread.php?t=1667929&nocache=1 to a T. However, when I go to flash, the file it's not there. No big deal... instructions say if this happens to go and mount data mount system and it should be there... however, it's not. Only when I unmount data does it appear. But when I do this I obviously get an error flashing it ("E:Failed to sysMapFile '/sdcard/cm-12-20150213-NIGHTLY-bacon.zip'").

So I figure I'll just sideload it. Following http://xdaforums.com/showthread.php?t=2559200 to a T. However, at step 11 twrp just says "Starting ADB sideload feature..." and has a scrolling progress bar that never stops. So I decide to just attempt adb devices and adb sideload commands but get a device not found error.

I would love some help/ideas on this! Thanks for everything in advance.
[ONE Original Android Development] strategist99:
thank for the reply mate, but i dont remember which PARTICULAR driver is installed as I had installed WUG's Bacon Root Toolkit and other stuff to get it rooted and working, thus I suppose its that driver only...

But ironically the MTP is very much fine till ver 2.8.3.x, so whats the catch in the upper versions?

regards