yashsingh1/xdaforums huggingface dataset:
[E 2015 Android Development] hajj_3:
instructions unclear, am i pressing power+volume down to get to recovery mode first? Do i keep the volume down and power pressed then let go of the power then single press or long press, do i keep the volume down pressed. Tried various things, need clearer instructions.

I haven't rooted the phone yet, not sure if that matters, i have just unlocked the bootloader and flashed TWRP from fastboot.
[E 2015 Android Development] ayush rao:
Okay.

Here are the steps:

1. First completely power down the phone

2. After powering down hold the power button and volume down till it boots into the bootloader

3. In the bootloader press the volume down button till u see recovery mode, then press the power button
[E 2015 Android Development] aksclusive:
TWRP 3.0.1 is now available... so please make a new update for surnia
[E 2015 Android Development] ayush rao:
Till Squid Rolls it out u can flash the official one on ur phone.

Here's the link

https://dl.twrp.me/surnia/
[E 2015 Android Development] codebot:
The size looks wrong. Maybe a debug build? Especially since they don't list surnia officially on the site yet.
[E 2015 Android Development] ayush rao:
I've been using it and have had no issues
[E 2015 Android Development] squid2:
Squid TWRP 3.0.1-r1

I've posted a new build from my TWRP fork. It's up to date with the upstream 3.0.1-0 release, though as always my fork has a few additional changes and cleanups. For this release, I have created a new dark green theme for my fork. I hope you like it. The download for this build is a bit bigger than earlier versions because of extra assets added for my theme.

[MENTION=5735382]aksclusive[/MENTION] - Please don't ask for new builds. I follow my own release schedule for my fork. Builds will appear when they are ready.
[E 2015 Android Development] EB20XY:
Great. Thanks. :highfive:

The new theme looks pretty cool. :cool:
[E 2015 Android Development] dwane3:
Sorry,but previous theme was better..How to get blue theme?Thanks.
[E 2015 Android Development] dzidexx:
@ squid2

Hi, can I flash new using old (3.0.0.r2)?

In twrp - "flash from image" or only in fastboot and pc? Maybe the Rashr apk?
[E 2015 Android Development] DroidFreak32:
The new theme looks really cool..But it doesn't match well with my ROM's and bootlogo's theme lol[emoji14]they're both a combination of dark grey and blue.

You can add custom twrp theme zips In the twrp folder in your internal storage.. There are many cool custom themes available in xda.. Just search for them ;)
[E 2015 Android Development] xpmule:
i like the theme, good to change it up.

So far so good though...but has the delete backup option been removed?

I am doing backup-up to sdcard now without encryption.

Normally i would delete my previous backup then make a new one.

This time i had to use the File Manager to delete the old backup. (other way was easier/convenient)

I don't know if it's a bug or what but my Timezone has been wrong for a few versions..

off by either 1 or 2 (i am suppose to be -8 gmt)

But cool though thanks.
[E 2015 Android Development] squid2:
For the time zone, you need to set it in TWRP settings. For deleting backups, I'm not sure how you used to do it, but what I always do is go to Restore, clock on the backup I want to delete, then hit the delete button that appears towards the bottom of the restore page.
[E 2015 Android Development] xpmule:
Ya sorry i should have said i meant the problem i was seeing was actually in the TWRP options.

And yeah i may have looked in the wrong spot for the deleted option "Restore"

I was tired looking before so i guess i might have missed it.

Thanks for your help / response though and the theme is cool and i am happy as long as they are dark based.

Dark themes are easier on my eyes.

And i figured i'd try and rag on ya about the time thing because if it is a bug

then i am trying to give you hard time about it ;) LOL

(it's mentioned early on for your mod-features on page 1)

To recap i am saying if i go in and check the time on TWRP i have to set it -7 to match all my clocks (verified)

And it's weird because it was working before some versions back normally.

I also know guaranteed i am in -8 (Kelowna BC, CAN)

Not a big deal though it can be offset in the options so i just wanted to report what i seen.

Want some ideas for a future version?

I have been using pretty much every version of your TWRP mod Squid and 2 things i like to do is..

- Turn down the brightness to maybe 70%

- Turn off all vibrations.

There is so much to TWRP it's taking me forever to explore the options / abilities of it.

And Squid your support for it has been a huge reason it's good.

You didn't just make a few updates & get bored and wander off.

Meaning we all understand you should do things on your own schedule.

I think i said get a Bitcoin address before for donations.. it's good idea !
[E 2015 Android Development] yelupic:
Time zone works properly right from the start:

The Czech language localization appears twice (Squid2).

Squid2's TWRP 3.0.1-r1

___

Official TWRP 3.0.1-0
[E 2015 Android Development] majster95:
Hi, i flashed latest version of recovery and i cant decrypt partition. Version 3.0 worked fine. Can you fix this ?
[E 2015 Android Development] yelupic:
Yes, decryption in (both, fastboot booted and flashed) TWRP v3.0.1-r1 doesn't work, using a lockscreen PIN with 8 ciphers. Data has been encrypted with a clean install of CM 13 @ 2016-04-02. - TWRP v3.0.0-r2 is able to decrypt data as expected.
[E 2015 Android Development] BillyMumphry:
Cannot flash TWRP!

Renamed file Recovery.img, placed it in SDK platform-tools, enabled USB DEBUGGING, put device in Fastboot mode, connected to PC, opened CMD window in platform-tools folder, typed "fastboot devices" ~~device identified, typed "fastboot flash recovery recovery.img" and I get error of cannot load file or cannot find file.
[E 2015 Android Development] yelupic:
if on a case-sensitive file system (Linux)

fastboot flash recovery Recovery.img

or

fastboot flash recovery recovery.img
[E 2015 Android Development] bloodsaw:
I see everyone always complaining about not being able to flash the file from their PC why don't people use flashify? I do and I never have issues when updating TWRP/Kernel/custom rom
[E 2015 Android Development] squid2:
Thanks for the heads up about the Czech language. The encryption issue you're facing is odd, as I don't recall actually changing anything crypto related. I hadn't tested it on surnia, but I did on osprey, which is essentially the same, and it seemed to work fine there. The main change between official TWRP 3.0.0 and 3.0.1 is my encryption changes from 3.0.0-r2 were merged in.
[E 2015 Android Development] yelupic:
OT @bloodsaw - Flashify - Tools are not for "apprentices", but hacking in a console making mistakes is the key to knowledge ... And people may ask questions.

---------- Post added at 03:46 ---------- Previous post was at 03:36 ----------

Thank you. - Please tell me, if and how I could provide you with more information to fix this (XT1524).
[E 2015 Android Development] yelupic:
[MENTION=6485916]squid2[/MENTION] - If it is of any use for you, here are some files attached.

SURNIA_RETDE_6.0_MPI24.65-39_cid7_subsidy-DEFAULT_CFC.info.txt

BUILD REQUEST INFO:

SW Version: surnia_retde-user 6.0 MPI24.65-39 25 release-keysM8916_2020629.41.03.21.51R

MBM Version: 80.20

Modem Version: M8916_2020629.41.03.21.51R

FSG Version: FSG-8916-02.61

Build Fingerprint: motorola/surnia_retde/surnia_umts:6.0/MPI24.65-39/25:user/release-keys

VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:

System Version: 24.51.39.surnia_retde.retdeall.en.DE

Model number: Moto E

Android Version: 6.0

Baseband Version: M8916_2020629.41.03.21.51R

Build Number: MPI24.65-39

Build Date: Thu Jan 28 14:23:33 CST 2016

OTHER MISC VERSION INFO:

Subsidy Lock Config: slcf_rev_b_default_v1.0.nvm

Blur Version: Blur_Version.24.51.39.surnia_retde.retdeall.en.DE

Version when read from CPV: surnia_retde-user 6.0 MPI24.65-39 25 release-keys
[E 2015 Android Development] BillyMumphry:
Flashify is for Root Users. I'm trying to flash TWRP so I can Root
[E 2015 Android Development] xpmule:
Sounds like you know what you are doing but i will throw this out there anyway.

Here is how i do it on Windows 7 x64 most times..

- Read page 1 for new version notes.

- Hit on downloads tab here then Download button and wait for it to complete..

- Open HashSlash.exe (or similar) and drag / drop the downloaded TWRP file then click on Hash File with MD5.

- Make sure the hashes match!

- I copy it to an archive i keep of collected and categorized Android files.

- For safe keeping i pack the version with Winrar.

- Then i copy the TWRP file into my mfastboot-v2.zip folder ("C:\Program Files (x86)\Minimal ADB and Fastboot")

Note: I have UAC set to OFF so make sure you have permissions.

- Then i open the ADB folder and put a 0 on the old Recovery.img file name. (or i just delete it)

and copy the new one into the folder, then rename the file "recovery.img"

- Then i run the following command saved from a text file i stored with misc commands.

Today i just added some to bat's again though. Note: Always use mfastboot (not fastboot) i heard it's better.

copy the following into a new text file and save it as CheckDevice.bat

mfastboot devices
@pause

- Important: Make sure you turn your phone off then hold Power + Volume-Down

( Let go of buttons when you see the Bootloader screen)

In case i hit a button by accident i leave it with restart Bootloader highlighted.

Plug phone in with USB cable making sure USB debugging is enabled in phone dev settings.

Make sure to wait until the tray icon for a USB device shows up.

Then run CheckDevice.bat and make sure you see the device model number otherwise troubleshoot..

(Make sure the phone is -NOT- in normal running state)

Then make another bat file or use command with console (right click empty folder space and hit open console)

Save a file with the below code as FlashRecovery.bat

mfastboot flash recovery recovery.img
@pause

- Run FlashRecovery.bat by double clicking when you see it say it worked close the window.

- Right click USB tray icon and select eject.

- Not sure it's needed at this point but i usually restart the Bootloader.

- Then select TWRP and verify it works.

Here is the Hashes for the 2 files i uploaded.

Hashslash.exe = MD5: 5095aa0c1b4d996096025461c97781ee

mfastboot-v2.zip = MD5: 590734d743cc9bf0e6a301246e036974

PS:

If you were on Linux guy then just ignore what i said :p
[E 2015 Android Development] BillyMumphry:
Thanks xpmule.....I'm going to give this a shot. I'll let you know how it goes! Right off the bat, I see some things I did wrong.
[E 2015 Android Development] yelupic:
Decryption with TWRP v3.0.1-r1 - More testing:

Flashed TWRP via fastboot

Booted into TWRP

Clean installed CM 13 @ 2016-04-02

Set initial lockscreen mode pattern 3x3

Encrypted the device

Rebooted into TWRP

3x3 - decryption worked

Rebooted into Android

Changing to a pattern of

4x4 - decryption worked

5x5 - decryption worked

6x6 - decryption worked

in TWRP

Changed over to lockscreen mode password (4 chars) - didn't work in TWRP

Changed back to lockscreen mode pattern 3x3 (new, not yet used pattern) - decryption worked again

Changed over to lockscreen mode PIN (5 ciphers) - didn't work in TWRP

Changed back to lockscreen mode pattern 4x4 (new, not yet used pattern) - decryption worked again

____

So, patterns are working fine in TWRP v3.0.1-r1.

Between TWRP v3.0.0-r2 (2016-02-13) and v3.0.1-r1 (2016-04-03) there has been this change in the code base:

https://github.com/omnirom/android_bootable_recovery/commit/a5db7121ab731d3d725ce77da46658dc098cfe45

If this is related to the PIN/Password field, maybe this is influencing the value/cursor position of the input field for the hidden passwort/PIN somehow in such a manner, that it's always wrong in the end?
[E 2015 Android Development] squid2:
Thank you very much for your testing, these observations are very useful. I just checked on my device and can confirm the same issue. I hadn't noticed earlier because I had only tested with a pattern password. I just did some testing and can confirm that they broke password entry. If your password is "1234", what is getting passed in to the crypto code is "***4". Obviously, that is broken. I'll be fixing it in mine soon, and will then submit a patch upstream. You can follow my version more precisely here: https://github.com/sultanqasim/android_bootable_recovery/commits/android-6.0

EDIT: You were correct in blaming that commit. Turns out that they totally bungled handling of password values. Their new code mixes up the value displayed to the user and the actual password underneath. I'll need to spend more time understanding how their text input code works for me to fix it. I presume they had a reason for this change, which is why I'm not just reverting it directly.

EDIT 2: Fixed https://github.com/sultanqasim/andr...mmit/09ec408c17c3661d47ce9d2d54bed60656ddf4b9

There are a couple more things I want to deal with after this, and then I'll release 3.0.1-r2.
[E 2015 Android Development] xpmule:
I tested backup + restore with Lollipop 5.1 on XT1527 and it worked fine (i used compression + no password)

I also am still seeing a 1 hour offset which is strange. (i have to use -7 when i should be -8 in TWRP options)

But i said before it's not a big deal just trying to report what i seen. (this has been an issue for many builds)

Also i always go into TWRP and make a backup after all those Google updates roll out occasionally..

THEN i copy the backup folder to my Windows 7 PC back up folder for safe keeping. (in case there is a problem with my SDCard)

Every version starting at twrp-surnia-2.8.7-r2 worked fine doing that until twrp-surnia-3.0.0-r2

(or possibly a version or two before that i have not made a backup in a while.)

Which when copying it would start then throw an error then crash windows explorer on me every time.

No idea why but it said the first time it did that my Phone stopped responding.

I quit trying and twrp-surnia-3.0.1-r1 came out and i tried it again and this time it's ok.

I thought maybe it had something to do with the Windows folder names.

(i tried different folder name variants etc but nothing worked)

And Squid2 yeah you were right i'm an idiot the delete backup was what i meant and where you said. it was.. doh LOL

So sorry i have no use for passwords or encryption or would help test that stuff.

I am an exhibitionist see my naked Android !!:laugh:
[E 2015 Android Development] bloodsaw:
if XPmule's steps don't help you try this

download and install minimal adb and fastboot http://xdaforums.com/showthread.php?t=2317790 and the Moto E Toolkit http://xdaforums.com/moto-e-2015/development/tool-moto-e-toolkit-one-click-unlock-t3047150

1.Enable developer options from about phone in settings by tapping build number 6-8 times, go back to the settings main menu and go to the new developers menu that appears above about phone and enable the android debugging option then using the Moto E Toolkit unlock the bootloader

2.reboot your phone into bootloader mode by powering down the phone then pressing vol down+power, flash the custom recovery using the Moto E Toolkit and boot into the custom recovery from the phone's bootloader, overwrite the stock recovery and your done.
[E 2015 Android Development] superstargoddess:
Newest version works great, beautiful default theme!
[E 2015 Android Development] squid2:
Squid TWRP 3.0.2-r1

The issue that prompted this release is a regression in 3.0.1 that broke password entry. I found the bug, fixed it, and my fix has also been merged upstream. However, I took this opportunity to improve various other things. I added in power management (frequency scaling and hotplug) to reduce the battery consumption of recovery. I did some cleanup and optimization to reduce the size of the recovery. I tweaked the theme a bit. I also updated various translations from the upstream gerrit.
[E 2015 Android Development] yelupic:
Squid TWRP 3.0.2-r1 (quick test)

Pattern, PIN and password decryptions work.

Second Czech language entry removed.

Very good and fast work.

Thank you.
[E 2015 Android Development] Dipandroid:
I am facing a weird problem suddenly. I have flashed the latest TWRP for Surnia but when I try to boot into the recovery mode it gets stuck on the TWRP logo for few seconds and then reboots normally. I've re-flashed the TWRP but nothing helped. I don't know how to fix this problem. Please help !
[E 2015 Android Development] BillyMumphry:
Thanks for all the advice and suggestions. After bricking my phone for 2 days I was finally able to flash Squids TWRP and am currently running a custom ROM. :)

Not sure of the exact procedure, it was a bit of a mad scramble, frantically researching Unbrick methods. I do know at one point after I was sure my flashings must have taken, I ran the command: "mfastboot continue" and the bootloader responded and the phone booted into TWRP.

---------- Post added at 05:35 PM ---------- Previous post was at 05:29 PM ----------
[E 2015 Android Development] bloodsaw:
[MENTION=5099355]BillyMumphry[/MENTION] Good to hear that you got everything working finally. also if you haven't checked out CrDroid, you should it's a great custom rom for this device and everything works on it.

[MENTION=6485916]squid2[/MENTION] I installed the 5.1 stock rom found here https://www.androidfilehost.com/?fid=24340319927534328 a little while ago about 2 1/2 weeks ago to update the modem and the bootloader also got updated but it seems to have caused some issues.

Anytime I restart my phone it loads up TWRP without me touching anything, for using the recovery this is great but as an everyday device it also kind of sucks. If I want to load android I have to use the bootloader, either I have to wait for twrp to boot then reboot into the bootloader and press power on "start" or I have to manually boot into the bootloader and press power on "start" . I can also reboot into the bootloader from CrDroid and press power on "start". Any ideas how to fix this? or if there even might be a way to fix it?
[E 2015 Android Development] xpmule:
So am i the only guy having weird issues with the time zone in TWRP

The last version i had to use -7 when i should be -8

Now with twrp-surnia-3.0.2-r1

I have to use -5 now.

I know i am comparing the time properly and i hit the TWRP set button etc.

I also just seen this after flashing Marshmallow from v5.1

by putting the TWRP in place of the official recovery before flashing.

EDIT:

I was not going to bring this up *again* but it seems to be getting worse hahahah

I also could see all the settings were reset just now too..
[E 2015 Android Development] xpmule:
Ok so i noticed before another big problem and forgot about it..

I installed Marshmallow (Telus) on XT1527

And i had substituted recovery.img with TWRP newest.. seemed to work ok aside from some time-zone bug.

But before and now again re-doing Marshmallow as soon as the OS boots

TWRP becomes inaccessible.. it shows the droid_operation graphic with "no command"

So this time i did nothing but drop in custom recovery and my custom made bootlogo.. then flashed.

Before and now it's giving me that problem.. even after i reflash TWRP again.
[E 2015 Android Development] bloodsaw:
ummm did you try turning on DST? tbh I had an issue with the clock myself with 3.0.0-r2 and setting DST to On with a 0 offset and putting it to Eastern Time(i'm from Ontario) made it work perfectly.
[E 2015 Android Development] xpmule:
Yup i Looked at that many times for many versions and it was always set to ON and always with offset 0.

And weird i just tried with it on or off and it didn't do anything.

I have had this issue going on with a million clean flashes going back to around 2.87-r2

The second bullet point on page 1 says.. "It reports the correct date and time"

It never really has worked properly for me a far back as i can remember.

So i wonder what exactly code wise he "fixed" and how.

I am curious if i am the only one though..

Oh and how can i ask do you set your clock to "Eastern time"

What does that even mean?

You pick a GMT offset based on what yours is suppose to be.

For example mine is suppose to be -8 (Google it.) Kelowna BC, Canada.

But it has to be either -7 or sometimes even -6 for me to get the correct time.

I have verified all other clocks i have are correct too online.

Anyway i am definitely more concerned with Marshmallow + TWRP ..it doesn't work.

I knew 6.0 would be a lot of problems which is why i waited till now to try it out.

SuperSU hahahha ..Now TWRP.

Messy nasty buggy untested stuff with little help out there.

It gets tiring having to reflash 100 times :(

EDIT:

Ahh i see where it says Eastern Time now LOL

..right beside the number offset.

I don't care what it says i focus on the numbers so i did not even really notice hahaha
[E 2015 Android Development] bloodsaw:
I had issues with versions before twrp 3.0 where I had to mess around with the offsets and DST settings to get the proper time to display. also if you read through my previous post carefully I mentioned in brackets that i'm from Ontario :P .

I recommend not installing SuperSU as it will mess things up like setting SELinux to permissive mode instead of using Enforcing mode also don't use the unofficial ports of CM 13 for Surnia I recommend using CrDroid and OpenGapps.org for Gapps packages it's what I personally use and the only issue i've had with CrDroid was one build the camera stopped working but Vatsal got that fixed in the build afterwards and it has been working like a charm ever since.
[E 2015 Android Development] xpmule:
Thanks for the tips i just want to let Squid know it's an ongoing issue.

Why i have no clue.. maybe something related TWRP but not TWRP itself?

I appreciate all suggestions i actually did not think to play around with the DST settings etc.

Stuff like this you have to check the dumbest things to make sure & rules out the easy stuff.

I just want to mention this occasionally and hopefully not piss off Squid.

I don't want it to seem like i am nagging him about it.

It's just that i mention it every version or two just to say hey i *still* have "My" issue.

I also don't *think* it's a serious issue either so..

I HAVE to have SuperSU even though it's risky LOL

I also lived in Ontario many years back so i get what you meant,

i was just being an idiot not noticing the options were numbered AND "named" for their regions.

I am patient ..i have been a cracker + coder for 20 years roughly.

Which means you need to absorb mass failure and fight bugs etc for as long it takes.

Liking trying to chip away at a cement wall with a tea-spoon LOL

A cracker knows he will have his target though.. he only sees the light at the ed of the tunnel.
[E 2015 Android Development] bloodsaw:
yeah I completely get that it's been an ongoing issue for you, I don't know how it would get fixed on your end though. If you absolutely must have SuperSU you'll want the versions in this post http://xdaforums.com/showpost.php?p=64161125&postcount=3 beta 2.67 works with android 6 I just find it slows down this phone specifically. Download SuperSU from the play store then flash the .zip file. The post I linked is for the versions that don't include a modified boot.img file so it's easier to find.

I've been on xda since android 2.2 got ported to the Xperia X1i by installing android to an SD card and having a boot process that runs on the nand flash there was even a dual-boot mod that existed so you could keep Windows mobile while having android installed it was a huge mess to set up but once you got that android running you were jumping for joy