yashsingh1/xdaforums huggingface dataset:
[Galaxy E5, E7 Q&A, Help & Troubleshooting] mtegg08:
Wanted to ask if your e5 camera glass covering the lwnse is crooked

Hi a.ay i just ask if your samaung e5 camera glass covering the lens is crooked. Mine has a little space on the right side of the glass inside the silver plastic frame. How about yours would youplease post some pics of your camera lens... thanks
[Galaxy E5, E7 Q&A, Help & Troubleshooting] mtadao:
Mine has no such space
[Galaxy E5, E7 Q&A, Help & Troubleshooting] mtegg08:
Pls post pic

hi Can u kindly post a picture of your e5 camera lens in good lighting covering different angles. Close up pls. I appreciate it thank you..
[Galaxy E5, E7 Q&A, Help & Troubleshooting] bo_hai:
It's okay

Flash it
[Galaxy E5, E7 Q&A, Help & Troubleshooting] piapemio:
Battery

I'm also from PH and flashed 5.1.1 from India, it worked, no issues but the battery is my only problem. I usually get 10+ hours medium to heavy usage but now I'm only getting 6-7 hours. Planning to go back to kitkat. :(
[Galaxy E5, E7 Q&A, Help & Troubleshooting] donaldistoopro:
same

The same problem here bro .. battery life is not that good anymore ... :( wish I could go back .. to kitkat .. or root my phone ... by the way

.. cm12 is .. under development now ... ..
[Galaxy E5, E7 Q&A, Help & Troubleshooting] piapemio:
Just flash the 4.4.4 firmware just like how you flash the 5.1.1 to go back :)
[Galaxy E5, E7 Q&A, Help & Troubleshooting] donaldistoopro:
tried already

I already tried that before bro

.. but when I reboot it gets stuck on the Samsung logo
[Galaxy E5, E7 Q&A, Help & Troubleshooting] Hassan 4:
That's because of the bootloader gets updated, It's not compatible with 4.4.4 Firmware, and can't be downgraded anymore.
[Galaxy E5, E7 Q&A, Help & Troubleshooting] Hassan 4:
Anyone upgraded to 5.1.1 can tell if Samsung enabled 64-bit in the OS or it's still 32-bit?

It has a great impact on performance if it's enabled, so please anyone check, you can download Antutu benchmark app and see the details about the mobile then see the OS is written 32bit or 64 bit

Thanks in advance.
[Galaxy E5, E7 Q&A, Help & Troubleshooting] mtadao:
Checked and its 32bit
[Galaxy E5, E7 Q&A, Help & Troubleshooting] piapemio:
I already flashed back to 4.4.4, just clear data if you're stuck on the samsung logo. Press volume UP + Home + Power to power up stock recovery.
[Galaxy E5, E7 Q&A, Help & Troubleshooting] t88:
I tried that and it went ok. I'm now using 4.4.4 because, currently, 5.x can't be rooted, at least for my model.

Sent from my SM-E500H
[Galaxy E5, E7 Q&A, Help & Troubleshooting] donaldistoopro:
Procedure

Really .. pls tell me the entire procedure sir .. please . Thank you in advance
[Galaxy E5, E7 Q&A, Help & Troubleshooting] piapemio:
Samsung logo stuck

Same procedure when you flash 5.1.1

download the 4.4.4 firmware, flash it using odin. IF you're stuck at the Samsung logo during boot, let it reboot again but now press "VOLUME UP + HOME + POWER BUTTON" to fire up STOCK RECOVERY, wait for the android logo to appear and from there clear data and reboot. This is what I did after having stuck at Samsung logo. Hope this helps
[Galaxy E5, E7 Q&A, Help & Troubleshooting] donaldistoopro:
Still didn't work for me .... sir are you using galaxy e5 ? I can't go to recovery sir ... because I can't turn of my phone .... galaxy e5 is built in battery .... :(
[Galaxy E5, E7 Q&A, Help & Troubleshooting] Hassan 4:
Hold your power button to reboot, Hold the power and vol up and home buyton for recovery, when it reboots release and hold vol up and home again.
[Galaxy E5, E7 Q&A, Help & Troubleshooting] one.moonshot:
Hi xpers!

Its fine to install the russian firmware on Galaxy E5 to?

Im from brazil, i download the russian firmware.

Model sm-e500m

Thx btw/:3
[Galaxy E5, E7 Q&A, Help & Troubleshooting] eabz2000:
You can't. Odin won't let you.
[Galaxy E5, E7 Q&A, Help & Troubleshooting] one.moonshot:
So, its just the firmware in my region?
[Galaxy E5, E7 Q&A, Help & Troubleshooting] eabz2000:
The problem is that the Russian version is for SM-E500H and you have SM-E500M. Samsung hasn't realesed the lollipop update for SM-E500M. The problem is the variant of the cellphone not the region.
[Galaxy E5, E7 Q&A, Help & Troubleshooting] one.moonshot:
Oh, OK. Tks for explanation ?
[Galaxy E5, E7 Q&A, Help & Troubleshooting] Endroyed:
How are you doing with reverting it back to KitKat?
[Moto Maxx Original Android Development] fgl27:
Support, any bugs and errors just post in here, I will answer as soon as possible.
[Moto Maxx Original Android Development] icondeg:
Can I flash it over using flashify?

Thx

Enviado desde mi Moto MAXX mediante Tapatalk
[Moto Maxx Original Android Development] fgl27:
i didn't try that only via fast-boot, but i will.

should not give any error, if you try let me know....

yes it work i just did over TWRP 2.8.1 :good:
[Moto Maxx Original Android Development] icondeg:
It works fine!!!

Thanks for all

Enviado desde mi Moto MAXX mediante Tapatalk
[Moto Maxx Original Android Development] Jaocagomez:
omg great work! congrats

muito obrigado!
[Moto Maxx Original Android Development] Gundabolu SC:
Awesome work! Thanks man! Can't thank you enough!! :)
[Moto Maxx Original Android Development] ChazzMatt:
Thank you!

Paypal donation sent.

Confirmation number: 08S12817NX2219226.
[Moto Maxx Original Android Development] fgl27:
Thank you guys i really appreciate the supporter. Of every one.
[Moto Maxx Original Android Development] fgl27:
Small, but big improvement change.

Change log in the 2° post. The TWRP now is much faster to wipe, restore or install a ROM, no more lag to format...
[Moto Maxx Original Android Development] icondeg:
Ok

I believe in you men

If you say that this no affect anything, that's fine by me

Regards

Enviado desde mi Moto MAXX mediante Tapatalk
[Moto Maxx Original Android Development] fgl27:
Update my source.

I can now compile TWRP from CM, Mokee and Omni source's.

Omni source is the best one because is the TWRP source, but it doesn't have quark device tree, so i need to create/port everything and that take time, i'm finishing the testing of the new TWRP no new feature just a more slim image but more complete.

My CM tree is incompatible with TWRP source, Dees_Troy was not able to use my previously tree to build the Official one he tried.

Now after the test i will send the new source and he will be able to produce a new TWRP from TWRP server and if that work make this Official.

+ Now that exist a quark device tree working on omnirom may some one make a AOSP ROM using it (i don't have time right now but i will try in the future after the Official TWRP).

Omni is the most close AOSP source to google AOSP so a rom from they is really clean and very update. I believe that CM kernel tree should work, if any one try let me know...
[Moto Maxx Original Android Development] icondeg:
What about a kernel??

[MENTION=2703206]w4tchout[/MENTION] is trying to make a kernel but it seems so hard to do it

A kernel that we can use is the second dream of this forum

Jejejeje

Regards

Enviado desde mi Moto MAXX mediante Tapatalk
[Moto Maxx Original Android Development] ChazzMatt:
[MENTION=2703206]w4tchout[/MENTION]
[MENTION=2228410]Skrilax_CZ[/MENTION]

Has Motorola ever released the mandatory kernel source code for 5.1 for the XT1254? Been two months since 5.1 was released for the Droid Turbo. It's a Quark, just like the XT1225...

I know [MENTION=2228410]Skrilax_CZ[/MENTION]j is using the kernel sources from stock 5.0.2 for CM12.1 (Lollipop 5.1). But would be nice to be able to use something from Motorola updated 5.1, if possible.
[Moto Maxx Original Android Development] ##W4TCH0UT##:
I don't know the actual problem as to why my kernel doesn't boot, it could be the dt img or the kernel itself. I'll try to figure it out though.
[Moto Maxx Original Android Development] fgl27:
I don't know much about Kernel yet so i cant see what is going wrong in yours...

But i find a workaround, to compile the recovery.img without compile the boot.img i generated a boot.img but use pre build dt + kernel.

That way i can compile recovery in under 13 min and without a kernel folder in the source, before it take over 30, and when i'm resolving bug and error, how much fast i can produce a image better.

The workaround i copy from victara and put in the omni folder of my device source, is need the mkbootimg.mk + dtb (dt image renamed) + kernel.

Then check BoardConfig.mk kernel lines, the dt and kernel i use from a previously build of my on, after you have one no need to compile the kernel every time...

Don't know if this will help but this way you may grub a previously working dt + new kernel or vice versa, and combine to see what works.

My CM source folder is working but not update do to that yet but i believe will work in others source other then omni.

if something work or not let me know.
[Moto Maxx Original Android Development] fgl27:
I finished all the tested with TWRP compile in omni source, i update the download link.

No need to change TWRP unless you use a encrypted device, or you wanna to test it.

Put a note about encryption on 2# post.

If any bug found let me know.
[Moto Maxx Original Android Development] respider:
glad to see someone resumed/restarted TWRP work for Maxx. Nice job buddy!

Unfortunately my Maxx was stolen back in Brazil so I wont use this as much as you guys.
[Moto Maxx Original Android Development] icondeg:
too bad bro

i hope you're ok

regards!
[Moto Maxx Original Android Development] colthars:
have flashed v4 today, first boot took 4 minutes counted on the clock. second boot took 40 seconds. everything running fine.
[Moto Maxx Original Android Development] jbirdyRazr:
Update: Hosed something so that Launcher kept freezing on me. Didn't make backup in TWRP (I KNOW)....... Didn't have the space in my storage... Too much stuff!........ Long story - short.......had to do clean start! Ever since restart, whenever I boot into recovery, it boots quick. Guessing that due to my storage being virtually maxed out, it may have affect on recovering boot times??? Just a thought...
[Moto Maxx Original Android Development] fgl27:
Storage space must not affect boot time... bootloader version maybe, I'm on 6.0.1 bootloader have no problem...

I didn't understand the "Launcher kept freezing on me" what launcher?
[Moto Maxx Original Android Development] jbirdyRazr:
I wiped Dalvik/Art cache and regular cache, thinking that might help/change boot times. That, for whatever reason, made a "Launcher 3 not responding" pop up - followed by a full screen freeze, requiring a full reboot.

I haven't jumped into Marshmallow yet - might try soon....great looking Roms out there now! I've stayed on CF's Rom(s) since Mofo. I need to stretch a little! Thanks again!
[Moto Maxx Original Android Development] ChazzMatt:
Ever since mod 2, mine always takes over 4 minutes to go from TWRP flash screen to the command options page. I'm used to it, don't know how to fix it. I'm on mod 4 now.

My wife's takes at least 2 minutes.
[Moto Maxx Original Android Development] fgl27:
Makes no sense to me, that is a 64gb quark right? using the latest boottloader?

my is 0x7093, you can see it by searching in get prop for "bootloader" in latest KA Logs I made...

I try to fill up my storage by making backups until it is full and the result is the same, bootloader to TWRP finish boot under 30 seconds always...
[Moto Maxx Original Android Development] ChazzMatt:
Yeah, we both have XT1225. Last bootloader I flashed was probably 5.0.2 from the CM12.1 thread about over a year ago.

I know where newer TWRP-flashable Marshmallow Soak 4 modem for XT1225 is (thank you for uploading it), and I flashed that today as part of upgrading to Marshmallow RR. Is there a TWRP-flashable Marshmallow bootloader? I can fastboot also, I guess, but I don't have any Marshmallow stock images downloaded. Is there a separate file already available somewhere?
[Moto Maxx Original Android Development] fgl27:
Understood...

Check CM13 OP for small zip with radio and bootloader for fastboot...

Is possible to have a TWRP flash for almost anything included bootloader, but I prefer not to produce a zip for that, TWRP will flash anything you tell to it to flash, so some one may brick a device and the bootloader it the fail safe it must be 100% ok all the time, and a wrong file inside a bootloader.zip may brick it...

Let me know if the result change if you up the bootloader... :good:
[Moto Maxx Original Android Development] gangrenius:
On my xt1254 Verizon turbo it takes a few minutes too boot also ever since mod 2 also. I just never said anything.
[Moto Maxx Original Android Development] ChazzMatt:
I just flashed the 6.0.1 Brazil bootloadervia mfastboot from the CM13 thread.

I already had the 6.0.1 radio (which I had flashed from your RR thread when I installed Marshmallow RR last week) but I flashed that again via mfastboot from the CM13 thread.

On bootloader screen, BL: moto-apq8084-70.93 (sha5c73flf, 2016-05-20 12:02:46)

I have actual numbers instead of rough guesses because I used her phone to time mine and used my phone to time hers. I hit reboot/recovery exactly when the minute changed on the big clock widget.

I rebooted from my normal GUI to recovery three times. From the time I hit reboot/recovery on the boot menu until I actually saw the TWRP command choice screen (install, wipe, et) average of about 4.5 minutes. Over 4 minutes of that time was stuck on the TWRP splash screen. It just hangs and hangs. Flashing new bootloader didn't make any difference...

On my wife's phone which still has CM12.1 and still has Lollipop 5.0.2 bootloader, I only booted into TWRP once (since I had changed nothing). From the time I hit the reboot/recovery on the boot menu until I actually saw the TWRP command choice screen (install, wipe, etc.) exactly 2 minutes. So, over 1.5 minutes on the TWRP splash screen. For some reason, her XT1225 is faster getting into TWRP command screen and has always been that way. Yet, until a few days ago we were running the same software OS version (CM12.1), same bootloader, same radio... I have more apps, but that shouldn't make a difference.

I can live with it, because it's been that way since TWRP mod 2. I'm used to it. Just reporting to you because you said it should take 30 seconds and that flashing new bootloader may fix the issue.

It is interesting having two Moto XT1225 side-by-side so I can compare stuff like this. (3rd one is still in the box, brand new. It's for emergency backup.)
[Moto Maxx Original Android Development] fgl27:
I see, this make things so hard... I make anything base on the result I have from my device, in here for a example the performance I achieve in TWRP is great, but knowing that is not true to all users makes really hard to know how to make it great to all, is probably not possible...

I have no idea what it can be, maybe my device revision have better storage support revised hardware, this is the only thing that make sense, I bought my last year if I remember correct it was manufacture in June or July of 2015 and is a Brazilian manufactured version (I believe it is just assembled here but it is a Brazilian made tag)...

But Ok... The Mod_2 V and up are build in Marshmallow source lets see in the future how is the performance of TWRP build in Nougat, I hope it is better :fingers-crossed:

:good:
[Moto Maxx Original Android Development] iiWoodstocK:
So just to throw EVERYTHING off, I just booked into TWRP mod 04 (from the recovery power menu option in RR) and from the instant the TWRP splash screen came up to when TWRP's buttons appeared was about 30 seconds.

However, taking a backup (~3850 MB) took about 10 minutes.
[Moto Maxx Original Android Development] fgl27:
To internal memory?

My s about 35-40 seconds it GB 32Mb/s in average TWRP says to me... maybe you have too much little files in data the number of files matter a lot...
[Moto Maxx Original Android Development] iiWoodstocK:
Yea. Off the top of my head, I believe the system backup writes at 9 Mb/S, and the data at 16 Mb/s

Though this time my backup was a bit more than usual. But my phone is pretty full (usually only enough room to make 1 TWRP backup) so that might be why.
[Moto Maxx Original Android Development] ChazzMatt:
Both our Puerto Rico and Mexico XT1225 we use daily were made in China at the Motorola factory there. In fact, the Mexico phone was shipped straight from China (I ordered it via Mexico Motorola website, and followed it via FedEx) to a Mexico XDA member's work address and then re-shipped by him to my U.S. home address.

The Puerto Rico one was Claro carrier and ordered through eBay dealer.

Puerto Rico manufacture date: 2014-11-15

Mexico manufacture date: 2014-12-04

Interesting mine is the "slower" to boot in recovery and was manufactured earlier than my wife's.

The 3rd one I own is also Puerto Rico. I bought it earlier this year for backup purposes. Still in the box, brand new, not rooted or anything.

Manufacture date: 2015-03-05
[Moto Maxx Original Android Development] quantum tao:
reboot to recovery from RR 1:30, used to be faster but seems fine to me.
[Moto Maxx Original Android Development] Claps1775:
Got a question. I installed this twrp on my 1st T1. I have this twrp also on my 2nd T1. I did a back up on my 2nd T1 and then put that back up on my 1st T1. I am not able to install that backup in my 1st T1. Is there something I am missing?
[Moto Maxx Original Android Development] ChazzMatt:
Migrate everything (apps and data) from one Android phone to another using TWRP Recovery

http://heavyjumbo.com/2013/10/13/mi...android-phone-to-another-using-twrp-recovery/

This was written in 2013, so not sure what's changed since then in TWRP -- but it talks about changing permissions and stuff which may be your problem.
[Moto Maxx Original Android Development] Claps1775:
[MENTION=3250376]ChazzMatt[/MENTION]

Thank you. That helps a lot and saves me a lot of time too.
[Moto Maxx Original Android Development] Claps1775:
Well, I got it all to work. But it failed to mount the modem. Will try all over again this weekend or I might just set the phone up the old way hehe.
[Moto Maxx Original Android Development] ChazzMatt:
Try re-flashing the modem in ADB?

---------- Post added at 11:24 AM ---------- Previous post was at 11:20 AM ----------

You are welcome! But please also hit the thanks on my comment, so others will know if it's helpful? Sometimes the "results" (follow-up comments) are not close to the original comment. If someone finds that comment via Google search (I do that all the time), having a couple of thanks showing means the advice is worthwhile.

Also, I post a LOT on XDA, mostly trying to help people or at least inform them -- and having thanks count closer to my post count shows I'm not just wasting time. ;)
[Moto Maxx Original Android Development] jco23:
I tried to perform a backup, and got an error message that the backup failed, yet a file was created. when generating the backup, I selected everything except for cache. i do have xposed installed on stock LP. am i missing a setting? version 3.0.2 mod on xt1254. i was able to make a backup on a prior version.

thanks!
[Moto Maxx Original Android Development] fgl27:
To make a backup, you select system, data + boot... others are just for others purpose, no need to backup recovery, no need to backup logo that doesn't change if you flash ROM, no need to backup Modem unless you are backing-up a old OS (kitkat) and will in the future after updating to LL or MM wanna to go back without flashing the radio, or the other way around.

Any way that backup "selected everything except for cache" works for me so I don't know what happens...

Without screenshots of the problem and the TWRP log, I have no idea what happens. next time print the screen and copy the log... advanced > copy log... file in internal memory like this:
[Moto Maxx Original Android Development] jco23:
tried again without boot, got same error message: createTarFork() process ended with ERROR: 255, Backup Failed. Cleaning Backup Folder.

under settings, nothing was checked; I have plenty of storage space; backup options has nothing checked; encryption was not enabled

I did see this regarding the error message (http://xdaforums.com/nexus-6/help/e-createtarfork-process-error255-t3302462/page2), but that was for the Nexus. The log is too big (~5MB) to post here, so below are the last few lines leading up to the error:

==> set selinux context: u : object_r:anr_data_file:s0

I:addFile '/data/hrdump.' including root: 1

==> set selinux context: u : object_r:system_data_file:s0

I:addFile '/data/hrdump.rdmp' including root: 1

==> set selinux context: u : object_r:system_data_file:s0

I:Error adding file '/data/hrdump.rdmp' to '/data/media/0/TWRP/BACKUPS/ZX1F22KQ32/2016-10-15--11-08-24_SU4TL-44//data.f2fs.win005'

Error creating backup.

I:ERROR tarList for thread ID 0

Error creating backup.

I:InfoManager saving '/data/media/0/TWRP/BACKUPS/ZX1F22KQ32/2016-10-15--11-08-24_SU4TL-44/data.info'

createTarFork() process ended with ERROR: 255

Backup Failed. Cleaning Backup Folder.

I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/ZX1F22KQ32/2016-10-15--11-08-24_SU4TL-44/recovery.log

let me know if you need the whole file and I'll be glad to send it to you. thanks again for taking the time to help, much appreciated! My plan is to install the Brazilian stock MM ROM with your kernel. So really hoping this works.
[Moto Maxx Original Android Development] fgl27:
have you try what that thread is point to the fix of the problem?
[Moto Maxx Original Android Development] jco23:
Not yet, wanted to get your input first. But it seems like simply flashing a new ROM would solve the issue.

I'll give it a try and report back. Thanks again for your responses.
[Moto Maxx Original Android Development] fgl27:
no not really that, ROM change doesn't directly affect data unless you erase it, you have a corrupted data file... I'm toking about post 3 the solution is there very simple one.
[Moto Maxx Original Android Development] jco23:
finally got it. deleted the hrdump.rdmp folder. looks that could have been created when I used Sunshine to unlock. after deleting the folder, a backup was successful.
[Moto Maxx Original Android Development] Epocilyps:
Not sure exactly what is going on, but I can't do anything from recovery. When trying to do anything, it goes through the motions, but does not actually do anything. I haven't been able to update nightlies for CM13 in a little while, but thought it was something with cyandelta and didn't touch it. Trying to flash a new rom and can't wipe anything. Says the wipe was successful, but all of my data is still there. I try to install new rom anyway, says it is successful and boots normally. So far I've tried downgrading TWRP, but that didn't help. Any ideas?
[Moto Maxx Original Android Development] fgl27:
this is confusing...

Data is where all your app are instaled.

Internal data, is fake sdcard folder.

if you wipe data will erase all yours app and they data.

So what are you doing and is not working?

After the problem happens, print the screen and copy the TWRP log... advanced > copy log... file in internal memory and share here.
[Moto Maxx Original Android Development] Epocilyps:
So, I tried running the copy log, and it gave me a blank, 0kb file which I'm assuming is useless.

IMG_20161224_194347 by Kyle Morse, on Flickr

This is a picture I took after attempting a full format, however. I'm not sure if this will help, but I just want to be able to do something at this point. Thanks, and Merry Christmas.
[Moto Maxx Original Android Development] fgl27:
TWRP can take a screen shot just like android, power button + volume down button...

Don't you read what is on the pic?

Disable "Simulate actions for theme testing" on TWRP Setting, and have a Merry Christmas.
[Moto Maxx Original Android Development] ChazzMatt:
Yes, you're right. Says "simulating actions".

It's actually telling you it's not really doing anything real.
[Moto Maxx Original Android Development] quantum tao:
LOL, good one.