yashsingh1/xdaforums huggingface dataset:
[Moto Z Play Guides, News, & Discussion] DroneDoom:
I'm not sure where you're coming from, have you ever altered your system partition? If you sideload through recovery, you would be able to see the recovery log and see the error it shows each time rather than having the OTA handled through the OTA client.
[Moto Z Play Guides, News, & Discussion] Jimi Mack:
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.

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

You installed this downloaded OTA or did you get yours OTA? Thanks.
[Moto Z Play Guides, News, & Discussion] xantanion:
Got my OTA today and had no issues. Just got the phone brand new yesterday as well
[Moto Z Play Guides, News, & Discussion] DroneDoom:
To unlock the stock recovery menu, bring up that 'no command' instance again and hold the power button and double tap the vol+ while still holding the power button. It's tricky, you may need to press them both at once or just play around with it until you see the menu.
[Moto Z Play Guides, News, & Discussion] Jimi Mack:
Thanks, I was able to get into it, but the sad part is I have no idea on what I am looking at, that might as well been a foreign language...lol. I saw several error logs, but as I said, no idea on what I was looking at. I did not know what to expect but was kind of hoping for a red lag or something that said "hey schmuck loot at this. "
[Moto Z Play Guides, News, & Discussion] DroneDoom:
If you invested in some Z mods and want them working (battery packs work but there's no software indication of charge or anything) you may have to flash some stock images to get everything sorted out. If you don't care then by all means you can use a custom nougat rom, the MM modem and radios still work even on a nougat rom.
[Moto Z Play Guides, News, & Discussion] Jimi Mack:
Hopefully at sometime there is a stock N rom I can flash from TWRP on a MM base.

Or I can try side loading yours and hope that works.

Question: What is the differences in the two "unsigned firmware" in the 1st post?
[Moto Z Play Guides, News, & Discussion] holabola:
Just got the update when I checked manually :D (Consumer Cellular RETUS Unlocked)

First impression: What an... interesting boot animation.
[Moto Z Play Guides, News, & Discussion] DroneDoom:
I think there may be a difference in security patches but they have the same build number so I'm not too sure.

Yeah it is, it reminds me of the days when I had a Motorola razr lol.
[Moto Z Play Guides, News, & Discussion] holabola:
For anyone that was wondering, the display size scaling works PERFECTLY.

I originally changed the DPI to make everything smaller, but it led to a lot of random issues with other apps (mainly involving the camera). The display size scaling mimics the effects of a DPI change right out of the box without all the issues and need for a computer (I wasn't rooted so) :D

Also, when I got the update, I was on the December 1st security patch.
[Moto Z Play Guides, News, & Discussion] xxBrun0xx:
Yeah motoblur might look like stock android, but it is very different under the hood. This is also the first 32-bit nougat phone in existence, and certainly the first nougat phone on the snapdragon 625. This phone is also unique in that it has to work with all of the Moto mods (none of the aosp Roms in the "ROMs" section work with Moto mods, so this probably wasn't trivial to add). For such a unique phone, we got updated pretty quickly. We got nougat before the Axon 7 (advertised as "daydream compatible" for +6 months before updated to 7.0) and plenty of other phones. It's not a nexus or a Oneplus, but Moto did good considering this isn't a flagship (although to most of us, it is).

Just want to be clear, Magisk v11 will brick on nougat. V12 works perfectly. I've got a whole thread dedicated to Magisk on nougat and was finally able to pass safetynet using s3v3n's 3.0.1 build and the latest v12 Magisk. Did not flash supersu or ARISE.
[Moto Z Play Guides, News, & Discussion] DroneDoom:
Thanks for the feedback (fixed op), I noticed v11 doesn't patch the kernel correctly and the ROM tries to boot without it. I thought it was just me since I was playing around trying to change my cache partition to f2fs but I guess the kernel doesn't support that filesystem for cache (ROM boots but doesn't initialize).

S3v3n's ROM is based on firmware stock right? I tried magisk with V4A module but it doesn't work and Atmos somehow bricks stock but it doesn't brick on a ROM built from different source (works on xperience). I noticed today that the ARISE project has a magisk module for it's latest project so maybe there's a possibility for stock to have systemless V4A.
[Moto Z Play Guides, News, & Discussion] Jimi Mack:
Question, when I am in Stock Recovery to side load the update, I ma getting this.. anyone know what Status 225 is?

Now send package you want to apply

to the device with "adb sideload ,filename>...

status 255

Installation aborted.

---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------

I think I may have found the issue, in Stock Recovery, is says :motorola/addison-retail/addison

but under ABOUT PHONE on the phone it states this is on a retus channel. Conflict of information, any suggestions?
[Moto Z Play Guides, News, & Discussion] DroneDoom:
Addison is our phone model's codename. For instance the Moto z variants are codenamed "griffin." They each have individual builds based on a region's network range and so they are codename as well...We are RETUS (retail US) which is the channel that we get our updates from so that each device will get specifically tuned update based on the region it represents. Reteu (Europe), retbr (Brazil) etc.

As for your 255 error, there is no specific documentation about this. It may be some incompatibility error or a failed sideload based on the same error # given in TWRP and CM recoveries.
[Moto Z Play Guides, News, & Discussion] Jimi Mack:
I thank you. I got the update to begin to load, it fails and aborts at 45% . It states something about content, lists my build number and give a code 755. I can not find out anything about this one either. I guess something is screwy with what is installed on my phone and what should be...
[Windows Mobile Development and Hacking General] mrabie:
Hi All,

First i would like to start out by saying that this forum is the best place to be if you are a WM (HTC) phones passionate user or developer and people here are really great and has a lot to offer.

Second.. As i see in this forum (Development and Hacking) that there a lot of developers who give a lot and ther who want to give a lot but don't know where to start. I see lots of potential in the applications being developed here and potential for lots of other applications that can be developed. MS in the past has kind of misunderstod the power and usage of touchscreen by making the UI of WM not really finger friendly, although they are starting to realize that (maybe after the iPhone came out) but we wont see that for another year or so when they come out with WM 7.

Anyway to cut the story short i wanted to say that almost everyday there's a new Finger Friendly app being developed and added to the forum and people with great ideas want to come up with new applications. We definitly have 2 killer applications PocketCM and PointUI that the developers have made a wonderful job in the UI, finger friendly and espetially the window transitions. They have conqured where MS has failed (so far) in providing the right controls for developers espeically UI controls to develop rich UI applications on their platform.

I was thinking why dont the developers of these applications share their platform with other developers here in the forum instead of each developer having to start from scratch everytime a new finger friendly application to be borned? especially that these applications are all free for download (that is if the developers of these application will keep providing these apps for free and not start charging like some other did)

That's just my thought and i would like to hear what other developers in this forum think and definitly would like to hear the opinion of the 2 wonderful fingerfriendly apps.

Thanks for you time in reading this and sorry for the long post.

Happy New Year 2008

cheers
[Moto 360] RawSlugs:
I have the first Moto 360 is there a way to get Android Wear 2.0 on it or are we getting an official update?
[Moto 360] Knxed_:
For the Moto 360 1st gen it will not be getting the 2.0 update same for the LG G watch. It's been confirmed it will only happen with the newer smartwatches. I mean there could POSSIBLY be a 2.0 rom but it probably happen in the future.
[Xiaomi Redmi 3 Questions & Answers] lalontra:
Hi All,

I have an Redmi 3 pro with unlocked BL and the latest "official" weekly 7.3.9 from xiaomi.eu and latest TWRP 3.0.2.0 from official twrp site.

I am unable to flash twrp.

I flash it with fastboot flash recovery recovery.img then boot into it using fastboot boot recovery.img with no issue at all.

Then,

if i reboot into recovery from twrp itself it still works.

if i let it boot the phone in its bootloader (POW+VOL_UP the one where you can choose "download" "fasboot" or "recovery") and i select recovery, it does not boot. The phone boots instead.

if i choose from the updater to reboot in recovery, same.

if i choose from flashify (which shows me "stock recovery" is installed), same.

if i use adb reboot recovery same.

i can only boot it using command fastboot boot recovery.img.

It just looks like the twrp flash says OKAY but it's not being flashed.

I've also tried cofface recovery with no success.

i've also tried official twrp app with no success.

everytime flash goes fine and successfully, but i'm unable to boot the phone in recovery itself.

i must always use fastboot boot recovery.img

Hints?
[Xiaomi Redmi 3 Questions & Answers] krasCGQ:
Hi [MENTION=3173995]lalontra[/MENTION],

Use combination of Power+Vol(+)+Vol(-) button. It should boots you to recovery.

Regards.
[Xiaomi Redmi 3 Questions & Answers] Axident_Formaldehyde:
It is error in this release ROM

You are not alone, its problem of this concrete ROM from 9.3.2017 ido.! You must flash different ROM, previous release.
[Xiaomi Redmi 3 Questions & Answers] lalontra:
Hi,

Did not work.

I have now reverted to 7.2.24 and TWRP from the TWRP from the phone is back. I think something is broken in 7.3.9 global weekly miui build.
[Xiaomi Redmi 3 Questions & Answers] complicazio:
For me works
[Xiaomi Redmi 3 Questions & Answers] phenomejohn:
The Volume+ and Volume- and Power worked for me even with the rom error. Hold all buttons til you see the Mi logo, then release Power but keep holding both of the Volume buttons. I also reflashed TWRP Recovery via Fastboot, so maybe that was it.
[Xiaomi Redmi 3 Questions & Answers] brittown:
I'm also facing a problem around TWRP 3.0.2.

But different situation

I always failed/unable to boot into recovery or bootloader everytime I click reboot recovery or bootloader button in TWRP recovery mode.

I still try to find a way how to fix it. Because all the articles that I found always explain about "cannot enter to recovery mode from the system", not from the recovery mode itself.

Do you got anything from all the steps above? Please let me know if there something u can share. Thanks in advance
[Xiaomi Redmi 3 Questions & Answers] brittown:
Here's what happened in my xiaomi redmi 3 pro. Always failed to boot into recovery again or into bootloader mode when I'm still in TWRP mode.
[Xiaomi Redmi 3 Questions & Answers] lalontra:
Update, once installed 7.3.23 all three buttons combination works!

What still does not work is adb reboot recovery nor reboot in recovery from update page, but this is fine to me.

Thanks a lot!
[Xiaomi Redmi 3 Questions & Answers] rubenix:
Hello there, Im also facing the same.

I can enter both recovery / bootloader from key combo but not from the system nor TWRP itself. I cannot really find a way to fix issue wich is kinda annoying for us flashaolics...

hope someone can find a way to fix it!
[Xiaomi Redmi 3 Questions & Answers] bayunugroho_9:
I'm facing same problem with you since updated to 7.3.9 Global Beta ROM.

I can only boot into TWRP by holding down Power + Vol Up + Vol Down buttons simultaneously.

---------- Post added at 11:59 AM ---------- Previous post was at 11:55 AM ----------

I'm still on 7.3.30, does it fixed in the latest update?
[Xiaomi Redmi 3 Questions & Answers] khoaphm20:
hi I'm using redmi 3s too. This problem happened when I flash new kernel to enable double tap to screen on :P I flashed twrp using both method: official twrp app and fastboot devices method...did not work but then power off the phone and use power + vol- + vol+ (works:)))) thanks for this post (note: for those who encouter this problem, when power + vol+ + vol- keep holding the 3 button until twrp logo on :)))
[Xiaomi Redmi 3 Questions & Answers] ravisghosh:
Thanks, it worked for me.
[Honor 8 Questions & Answers] Aniketkumar5676:
Hi,

Anyone Updated their Honor 8 Device FRD L02 B310 to B320

Through Firmware finder ???

:)
[Honor 8 Questions & Answers] qtoo941:
L02C675B320? Or C432 (Europe)?
[Honor 8 Questions & Answers] Droiderr:
he is talking about C675B320 on the indian H8
[Honor 8 Questions & Answers] s@j87:
Hi, is there any option to get oeminfo for Frd-L02C432?
[Galaxy Note 3 Q&A, Help & Troubleshooting] Ciaranow:
Hello, I am just curious :confused: is there a Note 7 ROM for the Samsung Galaxy Note 3 (N9005) that has a fully working Note 7 Camera with not maybe a few minor known bugs that you don't have to flash different patches for it?

I would appreciate any help.

Thanks,

~Ciaranow.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Ciaranow:
I am looking for a Note 7 ROM that has basic features that can get you round the day, Eg. Video calling - Ability to use data - Wifi - GPS - Full Note 7 Camera Functionality - Blue Light Filter - Always On Display - Full settings panel.

The list could go on. :3
[Galaxy Note 3 Q&A, Help & Troubleshooting] Ciaranow:
Not really. It might be a lot to ask but I have done my re-search and there are ROMS for the note 3 that have a selection of them but not all of them.
[Galaxy Note 3 Q&A, Help & Troubleshooting] philje123:
Phronesis 5.1 is my daily ROM. Very stable, very fast, good battery life.

Made me not need to bother upgrading my phone.
[Galaxy Note 3 Q&A, Help & Troubleshooting] shimsho:
download (Fougat Rom)

its had every thing you want

gps

Aod

n7 cam

stable

battey friendly

in one word , its awesome
[Galaxy Note 3 Q&A, Help & Troubleshooting] Ciaranow:
Hi, [MENTION=375661]philje123[/MENTION] but apparently the ROM you have doesn't have an ISO camera like the N7 and [MENTION=7940633]shimsho[/MENTION] does Fougat have the N7 ISO camera? If so, please tell me then I can try it out and possible help others by editing the post and saying what doesn't have the Note 7's features and what does.

I checked and the Darklord ROM has a lot of bugs however it does have the full fledged camera that the Note 7 has. This is proof there are ones out there however I would like one with less bugs and the full camera features with the AOD.

Any other listed ROM's would be useful.

Thanks,

Ciaranow.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Yousef_1337:
Try the Magma Note 7 Rom for Note 3 ? It's stable and my daily driver :) [MENTION=8135059]Ciaranow[/MENTION]
[Alcatel OneTouch Pop C7 Questions & Answers] voolandis:
I got bricked Pop C7 7041D Dual Sim as "gift", and I'd like to fix it. Phone has installed TWRP Recovery by hanuma50 v.2.4.1.0 - pretty much this is all I can do with it. It's unable to wipe system, I dont have any custom ROMs to try.

Reguar boot just loops from boot logo to white screen.

I tried SP flash tool, but it gives all sorts of errors, Mobile Upgrade S fails (cant connect to phone).

Computer sees it as Mediatek USB Device, but it keeps on connecting and disconnecting round and round?

Is there any way to make this phone usable?

Also, I can't do adb via recovery, as the computer does not see the phone.
[Alcatel OneTouch Pop C7 Questions & Answers] mattwhite7102:
I've got a solution if you wanted to try it, search on google MTXXXX preloader drivers, replace the X with your processor number, if you are not too sure of your processor number search up the Alcatel pop C7 specs on gsmarena, then once you downloaded the preloader drivers type in devmgmt.msc on the run command, this will launch device manager, then click on the top where it says username-PC, go to action > add legacy hardware, then click next, advanced, show all devices and then have disk then click on the folder that you extracted with the preloader drivers, then wait for the drivers to install, you will get a code 10 error, that's normal just ignore it, then go to SP flash tool and flash the firmware and you no longer got a bricked "gift", sorry if its a little confusing just read through carefully and you will be fine
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Awesomeness_1307:
Hey guys, I know a BEST ROM thread is discouraged, but I couldn't resist. Anyhow, there is a bucketload of options here and I just want a recommendation on which ROM I can use:

Here are my requirements:

1) It should be very stable, i.e., enough to be used as a daily driver. It will mainly be used for WhatsApp, Facebook Lite, and casual gaming (Mini Militia, BadLand 2, Into the Dead etc)

2) It should support Xposed.

3) It should support ViperFX.

Thanks in advance to anyone who might help. :D;)
[Android Q&A, Help & Troubleshooting] Delgoth:
Since these are too long to fit in post 1, I was forced to double post. Here is the last bit about partition tables. The reports are long. Please, any solid advice would be helpful.

***************************

** PIT File Examinations **

***************************

Moving on, I have used "PIT Magic 1.3 Release", found here on XDA, to look at the partition tables of the .pit files included with the N920AUCS3BPH4 & N920AUCU3APH1 ODIN firmware packages. I have also included the PIT File examination from the unlocked European Firmware. Given that PIT Magic 1.3 is a few years old, the latest version I have is labeled 2012. I read about how difficult it was to get the format correctly back then, and I have no way of knowing if the PIT File format has changed since then. But it does still seem to give usable output. I just don't know how to use this output meaningfully yet.
[Android Q&A, Help & Troubleshooting] droidvoider:
If you could hack one of the apps that are included in the sepolicy and set the Androidmanifest.xml to include android:dubuggable="true" we can make a two stage app. read and replace as root with the cow and then reload your inits.

toolbox.c root trick:

I am working on a very very powerful tool now. I am taking farm-root toolbox.c and changing it to grab root + context but then fork a process into a loop and just keep those privs. Hopefully I can even control that loop from the command line still! Currently I can get root and system_server, install_recovery.. But today after work we find out if I can hold on to it in a loop.

recovery-from-boot.p

I researched this today because we can read/patch this file with dirtycow. This file replaces the stock recovery every time you boot if they are different. I don't know if it also uses the hardware signature verification process, if so that's a key that's hidden in the partition image (hopeless for us i bet)

So if we replace recovery we have to crush this file with dirtycow.c
[Android Q&A, Help & Troubleshooting] verg0:
This sounds very interesting, i have a damaged g935f with dm-verty faied and frp lock so there is no way to use this device unless i flash with no-verity firmware but cant as frp stops me flashing root, hopefully you can use this exploit with the factory combination firmware to replace the boot loader with twrp or other custom bootloader to fix this issue, there is lots of people with same the problem im sure
[Android Q&A, Help & Troubleshooting] droidvoider:
Can you get booted at all? If you can' t get booted I won't be gaining access to that phone until someone smart works out the encryption, no one has on the note 3 yet not even hashcode (that he ever released). While the bootloader is locked.... The sboot.bin = signed by hardware key. If that key is not present there is an undisclosed backup key embedded in the partition, one must be present and neither are known. Minus the presence of those keys, chain of trust fails.

S7 is worth saving if it can be saved tho
[Android Q&A, Help & Troubleshooting] verg0:
No bud, the phone wont boot a normal firmware as the certificate is screwed and imei 0000000000, but it will boot with combination firmware, all i need to do is gain root and disable 'frp lock' via z3x box or another method and car repair the phone... Im not fussed about the warranty being void to be honest... I have ADB but not root fix phone :(
[Android Q&A, Help & Troubleshooting] droidvoider:
My tool will likely be helpful to you because that sounds good enough as long as you can get to a prompt that is CVE-2016-5195 / SVE-2016-7504 vulnerable. Anyone who isn't patched beyond Sept 2016 on any Android in the last 10 years will be able to use the tool I'm building to do amazing things. I am designing it precisely for people like you and Delgoth who have large investments in phones that could simply be repaired with enough access.

I am thinking now to fork off a child process anytime I can capture root + "any_new_context"... This will be forked into a child process then kept in a loop. If there is a new root + context that happens along through toolbox, we will grab that also.. (but I won't grab two of the same for example root + system_server I just need once)

I am hoping I can control this loop from the command line but since I am not the caller of the process for which I am capturing I am not sure that would work. This is new code to me, not sure of any examples of something like this. If I have to control it through values I set in files it adds a little more time. The great news is I am not having binary size problems so I can add quite a bit of code while still keeping toolbox much less than the currently installed version on my Note 5. File size must match exactly otherwise patching causes seg fault and seg fault ruins the fun (reboot to cure but irritating)

anyway just needed to come up for air I have a ton done, need to get toolbox fired up to test angle.. any c programmers that want to help or anyone with awesome ideas please feel welcome I could use help
[Android Q&A, Help & Troubleshooting] verg0:
Ah cool the combination firmware i have is:

COMBINATION_FA60_G935FXXU1APB5_STEP1_OLDFW\COMBINATION_FA60_G935FXXU1APB5_CL7345605_QB8752841_REV00_user_mid_noship.tar

The kernel is 3.18.14-7345605 Thu 25th Feb 2016 so it should be exploitable :) I'd love to get my S7 Edge working again
[Android Q&A, Help & Troubleshooting] Delgoth:
Do you have your toolbox on github? And is it commented decently? If so, I can look into helping with your code. I ask about comments because Ive not really looked into the whole. But if we figure out what parts samsung and at&t stripped down the AOSP toolbox, there could be a vector for completely patching the toolbox binary installed on our device.

Most root methods I see around, use busybox and su.

But our note 5 actually uses toolbox instead. Meaning, adapting a root method to use toolbox instead of busybox, eliminates that extra disk space taken up by the busybox binary, that needs to be patched in memory.