yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Ziyan:
So I did the Omnirom bringup yesterday, which is a requirement of official TWRP builds. I attached the TWRP I built with it, please test and report back if anything's broken :) I'll investigate this backup/restore problem some of you are talking about, to see if it's present in this build as well. What I do suspect is that decryption of a hardware encrypted /data partition isn't working atm - fixing this is going to take some time.

[MENTION=1608879]thepasto[/MENTION] I couldn't find your tree, so if you have any suggestions, feel free to contact me: https://github.com/omnirom/android_device_samsung_tuna/commit/8ef2f1059f54ed2cf2ab2738dd91dd28e5008f93
[Samsung Galaxy Nexus] bamtan2:
That sounds odd to me, but what do I know! ;) Thank you for your work!
[Samsung Galaxy Nexus] Ziyan:
Well, not directly, but TWRP builds from the Omni trees, so while a minimal device tree just to build the recovery would be enough, why not add full support while at it? :)
[Samsung Galaxy Nexus] chsaiteja98:
guys any one know how to prepare a twrp for lenovo a7010a48

as I have a7010 recovery working in it but can't flash ota updates any one help me in preparing a recovery
[Samsung Galaxy Nexus] :
That is the one I used. Everything got stuck after 600MB while restoring a F2FS data partition.
[Samsung Galaxy Nexus] osm0sis:
Is that with a new backup or one of your old ones made with a different build? If it's an old one, try to restore it with Ziyan's to see if that makes a difference, and if not, maybe try making a new backup to see if the problem persists.
[Samsung Galaxy Nexus] :
It was a new one, made with the same TWRP.

I would like to test but at the moment it is too much of a hassle :( If a backup restoration gets stuck then I can either wait for no-one knows how long for it to finish, or format the data and set up everything from scratch (or restore the apps using Titanium Backup which still takes time).
[Samsung Galaxy Nexus] thepasto:
I just add a comment to your commit.

About the backup/restore issue, i think it's only on cm13 kernel, so it should be fixed if you built it with omap4-aosp kernel

Thanks
[Samsung Galaxy Nexus] nailyk:
Hi,

Thank for the work and sorry for late,

I made some tests about encryption with your releases. TWRP-3.0.2-maguro-20160407.img and twrp-3.0.2-0-maguro.img.

Both doesn't decrypt the aosp 6.0.1 or the cm12.1. In fact I was never ask for a password.

I try to collect the most information but forget some :( (dmesg and crypto footer/header of aosp rom)

I doesn't understood well the 'f2fs bug' but i try to format and mount the /cache partition in f2fs file format and the both recovery tested work on it.

The encryption password of the cm12.1 is 'toto'.

Hope this help.
[Samsung Galaxy Nexus] :
It gets stuck when recovering larger partitions. I do not know what the threshold is but in my case last time it got stuck after reaching 600 MB.
[Samsung Galaxy Nexus] Ziyan:
The commit makes sense, it needs to known the default fs. You could make my job easier by submitting the fix to gerrit. :)
[Samsung Galaxy Nexus] thepasto:
I think i pushed it.. I'm really rusty!! :D Let me know if there's something wrong and if you need something more!

Thanks
[Samsung Galaxy Nexus] bamtan2:
From me (and the rest of the community): Thank you both for collaborating!! :) :good::good::good:
[Samsung Galaxy Nexus] radrj:
can someone please explain this to me
[Samsung Galaxy Nexus] Ziyan:
Please test the attached build with cm12.1, or any other rom not using hardware backed encryption (twrp support for that is still a work in progress) :)
[Samsung Galaxy Nexus] nailyk:
Awesome!

I think the screen shot is self-explanatory :)

Can you tell me what was missing?

Thank a lot for the job.

I will test the f2fs restoration asap.
[Samsung Galaxy Nexus] Ziyan:
The crypto footer location from the fstab :)

Looking forward to it!
[Samsung Galaxy Nexus] nailyk:
Thanks.

I did a test with f2fs /data but dont know if it is relevant.

I create a file with

dd if=/dev/zero of=/data/file.bin bs=8M count=87

save the full (encrypted) phone,

factory reset then format data in f2fs,

restore backup.

[MENTION=5038522]tomasz86[/MENTION] if you want you can provide me a full process (with backup?) to restore.
[Samsung Galaxy Nexus] kerpert:
Can you link the last f2fs version for GNexus?
[Samsung Galaxy Nexus] massima:
See post #1971.
[Samsung Galaxy Nexus] PythonNut:
I might just be dumb, but I can't seem to mount USB OTG in any of the recent TWRP builds. Is there anything special I need to do, or is it actually broken?
[Samsung Galaxy Nexus] nailyk:
For the usb otg the fstab says '/dev/sda1' but no dev sda was create when the stick was plugged-in.

I test with a usb-stick in vfat and a µsdcard in f2fs. (seems the µsdcard doesn't appears in dmesg).

Other info needed?

Edit: Yes, it's broken for me too
[Samsung Galaxy Nexus] massima:
[MENTION=6979267]nailyk[/MENTION], [MENTION=6906944]PythonNut[/MENTION]

See here
[Samsung Galaxy Nexus] nailyk:
Remember that but I think the [MENTION=2633638]Ziyan[/MENTION]'s version was based on omnirom and not on CM. So I suppose the kernel was different. I'm probably wrong. I give a try asap if someone can share a CM13 manifest.xml for maguro :o

Sorry for inconvenience.
[Motorola Droid 3] Sokini_:
Everything's in the title. As the chipset in the device has open-source specifications and map and assembler language, we sould be able to get it to execute our code at startup instead of Moto's, or at least flash the bootloader ROM, am i right? If not, please explain me why. If i am right, please tell me why we can't do it.

I am willing to use my phone as much as needed, and give devs as much infos as needed, as i can, did and will open it up as much as needed.

Thanks for your infos, feedback and help!

~Sokini_
[Motorola Droid 3] Dri94:
Assembly language is a bch lol. But thats interesting i never knew it was open. I hope a dev can explain
[Motorola Droid 3] MrObvious:
Tweet this to Hash.
[Motorola Droid 3] Sokini_:
Yeah, i mean id we could get logs from the bootloader booting (which we should be able to do finding the 4 debug pins on the board), we should be able to send instruction to the processor before the bootloader went booting and therefore bypassing the lock
[Motorola Droid 3] stevefxp:
It was my understanding that since the bootloader is encrypted there isnt a way to intercept this. Second since the boot image is signed I was under the impression that if we dont sign it exactly as Moto then it will fail.
[Motorola Droid 3] Sokini_:
Can't we write an open boot image and the just copy moto's signature (i guess we could get it from a hexdump and the just dd it to the file we're building)?
[Motorola Droid 3] ssinisterss:
i actually have a log from bug2go (motorola reporting thing) that randomly appeared on my sd card that has some bootloader or kernel number strings in the log. i dont know if its a key or just a random number.

edit: heres the string. i bolded the codes

========================================================

== dumpstate: 2011-10-21 18:11:39

========================================================

Build: 5.5.1_84_D3G-55

Bootloader: 0x0000

Radio: unknown

Network: Verizon Wireless

Kernel: Linux version 2.6.35.7-g790a33c (w30471@il93lnxdroid42) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Fri Aug 12 22:19:20 CDT 2011

Command line: console=/dev/null rw mem=512M@0x80000000 vram=4M omapgpu.vram=0:4M init=/init
[Motorola Droid 3] Senate9690:
That's just the kernel version should say the same thing if you go to About Phone
[Motorola Droid 3] SeiferTV:
Well, if we could "just copy moto's signature" we wouldn't have a locked bootloader at all, would we?

It doesn't work that way.

Think of the bootloader as a password protected .zip file.
[Motorola Droid 3] slayer621:
If that's the case, I say we all link computers and brute force it!

Kidding obviously :)
[Motorola Droid 3] Sokini_:
You can always crack a password protected zip file by using a pattern detector. There has been several recognized ways to do this over the years, and i don't mean bruteforce.
[Motorola Droid 3] Dri94:
Now this is getting into hacking. These developers are not going to hack or use bruteforce to crack the bootloader. Everything here has to be legal
[Motorola Droid 3] redsox985:
Radio HACK? That's an illegal theft of services and a TOS infringement, but how many of us did it? *raises hand now* Moto strung us along with the "end of 2011" unlocked bootloader lie, I'm in favor of doing it ourselves.
[Motorola Droid 3] misterpat1975:
Can't be any more illegal than rooting and flashing a custom rom.

Droid3/Liberty 1.2
[Motorola Droid 3] TriMesh:
I'm sure there are some developers on here that would try this - the problem is that it's an (intentionally) extremely hard problem. If you look at the cases where public key systems have been broken then it's generally because there was an error in the implementation that reduced the actual complexity of breaking them well below the theoretical one.
[Motorola Droid 3] Willis111:
Indeed, and that legality is questionable and depends on your network frequency. Warranty void != illegal

" Before the FCC started auctioning off the spectrum in block C some added regulations came into play encouraged by Google. The biggest regulation for licensing spectrum in “block C” is the “Open Access” provision. The provision says that those using the frequencies and “block c”may “not deny, limit, or restrict the ability of their customers to use the devices and applications of their choice on the licensee’s C Block network.”

What's illegal is the licensing violation on verizons part, the devs here are merely "using the devices and applications of their choice, this includes bootloader, kernel etc etc, all software on the phone except network/sim lock and any type os s/n on the phone that it is 100% illegal to alter.

Pretty much moot discussion now anyways, at least it will be once we see kexec working on our phones.
[Motorola Droid 3] Sokini_:
Doesn't apply to me, i bought it unlocked from moto and i live in france, so no problem with the carrier.
[Motorola Droid 3] Dri94:
I gotta admit i didnt read that paragraph so i dont know if its illegal not after what he said, i was simply just worried bout the thread getting closed and xda safety. Honestly, idgaf about if its illegal to the law lol. Id use it if it was. Moto shuld unlock it anyways
[Motorola Droid 3] redsox985:
I really don't think XDA cares much at all about legality (see radio hack as a major offender). That's just been my take from my time here.
[Motorola Droid 3] Willis111:
We care very much about legality here at XDA and have/enforce the policies in place immediately when issues arise (people posting warez, posting cp, changing imei/sn etc etc, illegal activities). Bypassing/cracking a bootloader etc to install desired software is merely exercising fair use of our phones, although it may be warranty voiding but so is rooting etc.

Check out our rules @

Forum & Marketplace Rules
[Motorola Droid 3] Dri94:
thanks for the verification :]
[Motorola Droid 3] hufn:
I was commenting on a similar topic on df earlier ;) I think the biggest issue that we are all overlooking is the fact that modders (meaning those putting on full roms and themes, not just rooting for ads and such) probably make up at most 1% of all motorola customers anyway. So the reality, why should they bother? A locked bootloader means that there are fewer chances a user can screw up their phone, and regardless of how it happens, when a phone winds up replaced, people can get annoyed or pissed. A negative review has ten times the impact as a positive one....

So it's not that they don't want us to, per se, it's that I don't think we even have an impact in the decision process at all. If their decision benefits us, great, but I would bet on coincidence...
[Motorola Droid 3] Willis111:
The % of people making the software might be that low but let's say 20% of all d3 users have ever flashed a rom(use the software), do you think motorola should just alienate 20% of its customer base? If you look at the moto forums every post is someone saying they won't buy another motorola and are going to samsung or htc or lg, any company that at least offers software updates. Unlocking a bootloader = voided warranty = more money for motorola through repairs (they charge to repair out of warranty phones) or replacements so imo it's lose lose for motorola not to unlock our bootloaders as well as in violation of their contract with fcc as far as I know. Also, providing software to unlock a bootloader means they would provide software to relock (back to stock bootloader) and wouldn't do any trouble shooting (I would assume) until you flashed back to stock with the software they would provide which would fix and errors caused by bad unlocks anyways (phones would get way easier for us to fix).

@Dri94 etc - glad to help clear it up a bit for you guys, wouldn't want you thinking that making fair use of your phone is illegal just because motorola will void your warranty, the code locking the bootloader isn't supposed to be there in the first place, was supposed to be removed in q4 2011 etc etc
[Motorola Droid 3] doogald:
I do not think that the number of rooters is anywhere near 20%. 2% may be on the high end. I think that most people just buy a phone and use it as is - a vast, vast majority, and that includes on all platforms.
[Motorola Droid 3] Endoroid:
While we can argue about the actually percentage of the modding community, we are no doubt the most vocal. We are the tech minded that can use social networking/media to spread a message around the internet. We are the ones likely to to paste a blog or forum with negative comments about a company. When your average user googles a phone they are looking at buying and see all the negative, even if they don't fully understand it all, they may choose to use a different company. And moving forward in time as the younger generation starts to look at buying their first phone, they are more likely to become modders, as young people these days are more tech savvy. The average end user isn't going unlock a bootloader anyways. Those of us that do are likely to be able to fix any software ****ups we make, so Motorola has little to lose and much to gain by unlocking bootloaders

Myself as any example, this device was the first android I bought, I knew nothing about roms and bootloaders. My next is not likely to be Motorola. And I know this is a common feeling for xt860/862 owners
[Motorola Droid 3] Endoroid:
And I got into modding by simply using google to try to figure out why the battery life sucked. One thing led to another...
[Motorola Droid 3] redsox985:
This was the first Droid I got into ROM'ing, I had rooted my DX for tethering and TiBu, but I seriously borked it trying to flash it with ROM Manager and didn't know what I was doing. Now that I know what's what about a phone, I will NEVER go back to a Moto device. I didn't know better with my DX, and I've since learned my lesson.
[Motorola Droid 3] Willis111:
I think I'll just avoid any company that offers a future bootloader unlock from now on, motorola, sony erricson (I had an arc and a play) etc and stick with samsung, htc or any company that offers a phone able to run a custom kernel out of the box as well as offering software updates to keep the phone not cutting edge but at least ~current... by the time motorola gets done "evaluating" ics for the d3 "jolly rancher" or whatever they call it will have been on the market for 6 months even though its being built for identical devices right now lol
[Motorola Droid 3] hufn:
Yes but we can make an educated guess - how many Droid phones have been sold so far across, what, 8-10 different models? It has to be in the millions, perhaps tens of millions? And how many users actually use roms and such - perhaps in the tens of thousands? Its hardly a scratch unfortunately...

Yes, they should, and some companies have done some positive towards the modding population, but the reality is that they really don't care all that much. It would be great if it was easier, and I send very high praise to those doing all this work!! However... what can you do?

I've stuck with moto because I want a keyboard, and they are practically the only ones. And, they do make a very good product overall. So you make choices...
[Motorola Droid 3] Sokini_:
Yeah right, it's not really much affecting their selling. But you have to remember that the people making the phones are techies to, they do like technology, they do use it, know how and love to. The ones to blame for the locked bootloaders on our phones are the marketing people and/or the carriers people.

Yeah, right, it does not affect their sellings. BUT it doesn't cost anything, and it would get them a great reputation, and would please the tech people, while not doing any harm.

I'm just begging for motorola to unlock it, or i'll just sell my phone and buy another brand's one.

~Sokini_
[Motorola Droid 3] doogald:
[Devil's advocacy] I think it *does* cost something. Every person who is not technically proficient enough to understand the process of rooting (and recovering with command-line tools like Fastboot) who calls for support has a cost to Moto for handling the call (which is probably solved by doing a refurbished phone exchange - there is a cost for that.) We've all read plenty of posts from people who have tried to root their phones who probably never should have tried. I am sure that their support costs (which are passed on to all of us - it's a cost of doing business for Moto that they will try to recover) are lowered by locking the phone down and doing something like they are planning to do with the dev Razr - sell the phone at full price to somebody who accepts it as-is, with no warranty or support from Motorola.

So, I do think that dev program - no subsidy, no warranty - is a fair cost if you want an unlocked phone. [/Devil's advocacy]
[Motorola Droid 3] Sokini_:
@doogald Alright then. I accept your arguements, and they are right.

But then again, let's them do like HTC did. Just let us void our goddamn warranty and unlock our ****ing phones. I am ready for that, as long as my phone is unlocked.

Come on motorola.

Please.
[Motorola Droid 3] doogald:
I agree with that 100%. Make people sign away their warranty or something in exchange for a key to unlock the bootloader. I'm all for it.

In fact, I will go further: I think that they should provide the tools that will allow an owner with an unlocked bootloader to bring the phone back to stock, if that's what they want. If your phone bricks, tough luck, but what do they have to lose if you are already unlocked anyway?
[Motorola Droid 3] Endoroid:
But this could be solved by having a unlock/relock/flash stock utility. When someone bricks, plug the phone in and the utility fixes it. Instead we rely on leaked files, and unofficial methods.

And I also don't agree with the no warranty. I buy a phone and it has a true manufactures defect, tough **** you bought a dev phone. Limited warranty would be much better. Fixing defects like malfunctioning volume rocker, etc. Void warranty on software, cpu, etc. Things we can actually affect

Just my 2 cents
[Motorola Droid 3] redsox985:
I would sign away the portion of my warranty that covers software. Hardware defects should still be covered by Moto for the year or whatever we get because those kinds of defects can't be caused by us. Give us a stock repair and unlock utility. If we are so inspired to unlock the bootloader, we surely know how to flash stock software back over it. It wouldn't be tough for them to do. If you mail back a phone with that is bricked with an unlocked bootloader, they can just send it back to you and say tough luck, fix it on your own.

Hardware issues should be covered, software shouldn't, for the extent of the warranty, if you unlock the bootloader.
[Motorola Droid 3] doogald:
My guess for the reason that they make the phone as-is is because a phone with an unlocked bootloader can be overclocked. The issue is that with a bricked phone from overclocking it would be nearly impossible to tell what caused the hardware failure.

You could also run the wrong driver for the speaker and blow it out; the same with the camera. There are any number of issues that could happen from running a custom kernel and ROM that could cause hardware failure.
[Motorola Droid 3] trisonics1:
Me too. Using Verizon D3 with XT883 ROM in India. :)
[Samsung Galaxy Nexus] Esteway.619:
Nice. Had this on my nexus s 4g and loved it.
[Samsung Galaxy Nexus] fcisco13:
Will nandroids from other recovey work??

GNEX
[Samsung Galaxy Nexus] RussianMenace:
Definitely will be keeping an eye on this. Great work.
[Samsung Galaxy Nexus] mrkmrk:
I can stand bugs, but taking a full minute may be a but much, considering how often I am in recovery. I'm really happy to see it here, though, and can't wait for a more finished product.
[Samsung Galaxy Nexus] jerrycycle:
From past experience, no. Different file format used in the backup from this recovery and clockwork.
[Samsung Galaxy Nexus] Viper87227:
gunna give this a shot. TWRP was awesome on my E3D

EDIT: Working good so far. Screen formatting is a little odd, but not a big deal. The 60 second boot up was a little odd too, but worth it.
[Samsung Galaxy Nexus] fcisco13:
Back up in 76 seconds!! File manager!! Win!!

GNEX
[Samsung Galaxy Nexus] joshw0000:
I'll definately be following this. I use Boot Manager so I'm only in CWM if a rom wont boot. Once the 60 second issue is fixed, this will be a daily recovery for me. Thanks!
[Samsung Galaxy Nexus] Gil Smash:
Using this now and even with the bugs it kicks ass, thanks!
[Samsung Galaxy Nexus] MONKY_1:
same here once the 60 secs is gone this will be my new recovery!
[Samsung Galaxy Nexus] atoy74:
For whatever reason, mine didnt take 60s to come up. I wasnt timing it but it was a reasonable amount of time.
[Samsung Galaxy Nexus] AmericanJedi001:
Thanks Dees_Troy and the rest of the TeamWin team, I've been hoping to get a chance to try out TWRP, it sounds very promising! I'm looking forward to future releases that iron out the kinks. Thanks again!
[Samsung Galaxy Nexus] weirddan455:
What does it do that clockworkmod doesn't? Except take forever to load. No one's gonna wait 60 seconds to go in recovery. Booting all the way into Android doesn't even take that long. And clockworkmod touch has been around for a while so get that if you want the touch feature.
[Samsung Galaxy Nexus] my95z34:
The interface is 100x better.... And are you in such a hurry that you can't wait a minute to boot into recovery? It's not that serious.

I've never liked CWM so this is a no brainer for me. Plus CWM Touch is just the standard CWM with added touch. Seems cheap to me. TWRP 2 is a completely touch orientated recovery, built from the ground up to do so.
[Samsung Galaxy Nexus] fcisco13:
Ummm..

Que files to flash.

Half the time (if not faster) to backup/restore.

That alone does it for me.

GNEX
[Samsung Galaxy Nexus] Dees_Troy:
Proper working builds (no more preview build) are now available!
[Samsung Galaxy Nexus] stangdriverdoug:
Sweet thanks!
[Samsung Galaxy Nexus] grim281:
Every zip that I try to flash errors out and fails. Using a verizon gnex.

*update* I flashed the recovery through fastboot and it works fine now. Not sure if something is up with your recovery zip.
[Samsung Galaxy Nexus] jesusice:
Another reason to use TWRP: http://www.reddit.com/r/Android/comments/vvq3w/taskertwrp_recovery_autonandroid_backups/
[Samsung Galaxy Nexus] segv11:
Secure Settings is not actually required; Tasker has "use root" checkboxes.

EDIT: If you want "use root", you need to choose "Run Script" not "Write File".
[Samsung Galaxy Nexus] Anon9mouz:
Hey dees quick question I see battery stats and rotation was took out any reason why? I know its not really needed but just wanting a technical answer thanks homie

__________________________________________________