yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Questions & Answers] jawz101:
I have the US model and I won't use tenfar's method on the phone for which it's intended. It's a questionable method
[ZTE Axon 7 Questions & Answers] andrew97b:
Unlocking your bootloader and Flashing CM13 is pretty easy and I don't really think there is much risk of permanently bricking your phone. However as of right now it really isn't worth the effort. I flashed CM 13 yesterday and it ran well, but the camera wasn't working so I decided to go back to the stock software. So unless you don't need the camera I'd skip flashing for now.
[ZTE Axon 7 Questions & Answers] 3165dwayne:
lag?

ok, where is this lag? I've been using it stock since I got it after the Note 7, which was very laggy, and have failed to notice any lag.
[ZTE Axon 7 Questions & Answers] rendler:
Zero lag here as well, buttery smooth at all times. Heads and shoulders above the Note 7 that I came from in terms of responsiveness and general performance.
[ZTE Axon 7 Questions & Answers] xtermmin:
On the US model, you can get an unlocked bootloader & all the trimmings without using tenfar's tool at all, although it's a bit more of a roundabout method.
[ZTE Axon 7 Questions & Answers] borijess:
Just unlocked mine working great.
[ZTE Axon 7 Questions & Answers] StoneTrapper:
Hi,

Just thought I'd add as I'm one of those who did end up in DFU mode permanently. I have a reasonable understanding of the issue at hand and I've been one of the few who have been vocal about not calling the current method safe of us.

My suggestion if you have a A2017G is not to bother using tenfar's tool unless you're willing to RMA or make use of your warranty. I'm not in a position where I can do that, but since most are there hasn't been much interest in a solution.

I don't have the firehose itself to begin working on fixing the issue, though I do have a rough idea of how do so using the partition table for TWRP but I don't think I have the time to learn how to put it all together myself. Particularly when I'm replacing my Axon 7 with a Mi Note 2.

What is needed is an unbrick tool, ZTE have made and released them for their own devices before, why they don't do that with Axon 7 is beyond me.
[ZTE Axon 7 Questions & Answers] keessonnema:
You must be using the US or CN model, because the EU model is laggy as hell. It's by far the laggiest ROM I used on a phone with high-end specs..
[ZTE Axon 7 Questions & Answers] rendler:
Yup, using Chinese model with 128GB of storage.
[ZTE Axon 7 Questions & Answers] razorblader:
Just my 2 cents having unlocked the bootloader on my A2017G. I used tenfar's tool to backup the boot and stock recovery images and flashed the TWRP recovery and didn't run into problems fortunately. I wouldn't recommend to flash the rooted boot.img by tenfar until (hopefully) we'll have a unbrick tool for the G version.

My recommendation ----- On the G version don't mess around with the bootloader! ----- My recommendation

I've been able to unlock the bootloader on B03, reflashed stock recovery with tenfar's tool and successfully updated to B05 from the SD card.

If you want root I recommend to go the unlock bootloader - flash SuperSU 3.65 route instead of flashing the pre-rooted boot.img from tenfar with a locked bootloader as chances of things going haywire seem to be greater with the second method on the G version.

In case you have any reservations I definitely recommend to wait for a unbrick method of the G version before you try any of this. If and when such a method will come is undetermined at this point in time.

@lag of G version: Can't confirm that on B05, everything running smooth so far. There are a few graphical glitches though (stock browser displaying left side first und has sometimes trouble to show the content fullscreen.

Pull down notification bar has double lined icon text slightly cut off on the bottom once you switch to landscape mode and pull down the notification bar.
[ZTE Axon 7 Questions & Answers] rczrider:
I've seen this said a couple of times (or maybe it's just you in different threads, I don't know), but I don't understand it. By its very nature, rooting your phone is "questionable". Why is tenfar's method/tool any worse than any other method or tool? Do you have some technical insight to provide (and if so, please do so) or is it just an opinion based on nothing? I certainly don't have any issue with the latter, but I find it odd that people without any technical expertise speak as if they're an authority of some kind.
[ZTE Axon 7 Questions & Answers] jawz101:
It's probably me and a few others. Ok, answer me these questions:

What does the tool specifically modify on the phone?

What is a "firehose mbn" anyway? Tenfar mentioned it is how it gains access to the phone. I don't know if that is a tool to do so or if it's a file that gets put on the phone in a more permanent chipset-level storage only meant to be altered by Qualcomm or phone manufacturers. I'm find with replacing a recovery, kernel, ROM- the boot.img or anything lower than that is closed source for a reason. Probably because it's talking directly to the hardware and code at that lower level can circumvent anything in a kernel, recovery or ROM.

Would it affect Snapdragon SmartProtect?

https://www.qualcomm.com/products/snapdragon/security/smart-protect

Why do virus scanners call it a Windows trojan if it's an Android hack?

Yes, I call it questionable because I have questions. Since the file is encrypted you can't answer those questions for me. All I can gather is everyone who has used it has basically said "I used it and it did what I wanted it to do so it must be safe."

---------- Post added at 10:20 AM ---------- Previous post was at 09:46 AM ----------

@rczrider

Here are the posts in the thread by a security expert asking questions about the method.

http://xdaforums.com/search.php?searchid=430010789

Here is tenfar's response to him

http://xdaforums.com/axon-7/develop...r-unlokced-t3441204/post68301899#post68301899

Here's a post from him on ZTEUSA

https://community.zteusa.com/message/50425

Here's a blog post he made about it

https://blog.onedefence.com/signed-firehose-images-and-why-theyre-dangerous/?pk_campaign=zte-forums
[ZTE Axon 7 Questions & Answers] peramikic:
OK, It would be nice if people would inform themselves about this but unfortunately this is the state of XDA now... so here we go

- Firehose is a protocol used to communicate to the qcom chipset directly at a level lower than OS. Since there are security measures in place, in order to talk to it you need a signed firehose withe a coresponding certificate that is burned into the SBL. This is what ZTE uses to directly flash the units at factory and can also be used at repair centers. Tenfar is in possession of such a file and his flasher utilizes it to write modified boot and recovery that would otherwise be discarded by SoC's security protocols. Since it's obfuscated code to hide the firehose plus in addition uses comm libs and code that probably reads and writes other files, it is no wonder it gets flagged by AV software. I had ODIN flagged by Avast once.

- The boot.img is not closed-source, it is actually kernel and ramdisk and can be unpacked so you can see what's inside. It can be compared to stock as well and in fact that is exactly what his are, patched stock boot images. The boot image has been patched in order to allow the modified boot img with root to boot since SecureBoot is still in place due to locked bootloader. In addition is modifies SE Linux to allow root to run. And that brings us to why this tool exists in the first place. It is to allow you to

bypass

SecureBoot and have root and was created in the period before unlock method was provided by ZTE. It is still the only method to use on non-US model. It is a hack tool by definition and has made development on this phone move ahead way further then it would.

- The security concerns raised were more along the line of how bad it is that the signed firehose is in the wild, not so much to what tenfars tool does or how it does it. The expert even wanted the firehose to be posted on the forum(SMH), which tenfar refused since he did not wanted it to spread and hence obfuscated the code. The signed firehose would present a security vulnerability if someone came in physical contact with your phone since they could dump data or load something on it without your knowledge, as pointed out on the sec blog and other posts, but it has nothing to do with whether you use tenfars tool or not.

- Smart Protect is an API feature that the an AV app would have to use, it exists in the SoC but does nothing on it's own so is irrelevant but i figured i'd clarify it (again)

Most either understand that or don't care. This is the XDA, where we break our warranties and bypass SafetyNet in order to have different emojis ;) Thanks to tenfars tools i have noticed that ZTE has broken the FDE on their stock builds since TWRP was able to decode /data with default password even though it shouldn't. So in my book it's a net plus, at least i know how unsafe it is now.
[ZTE Axon 7 Questions & Answers] jawz101:
Would that be this method?

http://xdaforums.com/axon-7/how-to/bootloader-unlock-t3437778/page1

And thank you [MENTION=1340661]peramikic[/MENTION] for the answer. I've been googling forever on the mbn stuff but never found much on what it exactly is save that it's a manufacturer's tool. This clears up a lot for me. My biggest concern was if an mbn was something that actually rewrites code on the chip itself. Sounds like it's just an external tool a manufacturer uses to put their image onto the phone.
[ZTE Axon 7 Questions & Answers] peramikic:
No problem. The mbn itself is just a file format. In this case it has information about emmc partitions. It is also signed with proper certificate. That let's it talk to the chip and is pretty much just a low lever read/write interface.

As far as that method linked, it will work only if you are on the B20 release, US model only. The file looks for a particular build signature as well as partition signatures so it will not flash on anything else.
[ZTE Axon 7 Questions & Answers] jawz101:
Yeah. At this point I think I'm too lazy to futz with downgrading, patching, then upgrading, and all that. Probably just go with the tenfar tool then 0_o
[ZTE Axon 7 Questions & Answers] xtermmin:
Yeah, I used that method because I was already on B20, and my PC runs linux so :effort: to setup a Windows VM to use tenfar's tool. Using that (ZTE's official B20_Boot) and ZTE's official B20 image, you can have an unlocked BL and be on B29 without using tenfar's tool.

tl;dr: Whatever version you're on -> B20 -> B20_Boot -> unlock BL -> B20 -> OTA to B27 -> OTA to B29 (-> flash TWRP, SuperSU, whatever)
[ZTE Axon 7 Questions & Answers] Controllerboy:
UPDATE:

After days and weeks of doubt, I decided that for now, I'm just not going to risk bricking my phone with tenfar's method, I'm really just too scared. You need to know that last July, I lost my Oneplus One at a festival. A few weeks later, I bought a used Nexus 5x. Just two months later, I fell into a ditch when drunk and the phone took a plunge with me. I really don't want to lose my A7. For now, I'm going to wait and just pray a safer method comes along for us Europeans.

For A2017G users who do want to take the risk: here's the list of findings I compiled this afternoon when roaming XDA for answers on what to do/what to avoid.

If someone could just help us A2017G users, I'm sure we could all shell out a few euros...
[ZTE Axon 7 Questions & Answers] Bucci83:
so I used the same method, I'm on B29 with Unlocked Bootloader but now I cannot flash the TWRP recovery, I get :

target reported max download size of 536870912 bytes

sending 'recovery' (13536 KB)...

OKAY [ 0.315s]

writing 'recovery'...

FAILED (remote: unknown command)

finished. total time: 0.335s

any Ideas on what's going on?

I'd hate to have an unlocked bootloader and not being able to root :(
[ZTE Axon 7 Questions & Answers] xtermmin:
I take it that you flashed the full B29 image from the ZTE website.

The full B29 image contains a fastboot.img that does not accept the recovery flashing command.

My little process was made before ZTE posted the full B29 image.

Try using the tennear tool to flash TWRP recovery.
[ZTE Axon 7 Questions & Answers] Bucci83:
I followed this process https://xdaforums.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715

but you are right, after unlocking the bootloader I was on B20 and I flashed B29 from ZTE Website...

although after not being able to flash the TWRP I re-flashed B20 and then followed the steps in the post I pasted, however I didn't flash the B20_UNLOCKABLE_BL.zip

do you know if that will fix the problem?

can I get back a fastboot.img that allows to flash TWRP?

I tried to use tennear tool but I get "failed to connect"

**EDIT**

I downloaded the Qualcomm drivers and I was able to read the recovery and boot img, now when I try to write the program closes/crashes

I've tried the following:

axon7tool -w recovery

axon7tool -w recovery recovery.bin (renaming the twrp file obviously)

axon7tool -w recovery recovery.img (renaming the twrp file obviously)

no luck... any suggestions?

I'm close!!

**EDIT-2**

Finally! I was able to flash TWRP I've found a post that said to put recovery.img and recovery.bin in the same folder, It worked maybe you just need one but let's put both to make sure :)

Anyways thanks "xtermmin" to point me in the right direction, appreciate!

for the record I have an Axon7 US with B29, TWRP 3.0.2 and Root access
[Xiaomi Redmi Note 3 Guides, News, & Discussion] look4sky:
it is really great list out here good feature in miui 8
[Xiaomi Redmi Note 3 Guides, News, & Discussion] PoseidonKing:
Hit Thanks button if this thread helped you!

Regards,

PoseidonKing
[Xiaomi Redmi Note 3 Guides, News, & Discussion] PoseidonKing:
Thread Updated

Screenshot feature added!

Regards,

PoseidonKing
[YotaPhone] The_Rusty_Geek:
Hi, I recently purchased a YD206 from Gearbest at an amazing deal (only 130 for this phone) and as of my usual habits, I checked the XDA forums for the Yotaphone to see if there were any ROMs or tools that I should download. The phone runs on 4.4 KitKat, but I would need to upgrade to 5.0 to use many features. I had a Nexus 7 (2012) that was slowed down and made unusable because of the 5.0 update, and people here say that 5.0 slowed down their phone too. If I want to upgrade to 5.0, what build should I use? (I live in the US).

After I update the phone are there any interesting things to download/check out?

Thanks.
[YotaPhone] kingtiamath:
The Last russian firmware works very well and its lollipop. It also has several new features you dont get in kk

Enviado desde mi SM-N930F mediante Tapatalk
[YotaPhone] VirtuaLeech:
Upgrading to the latest Russian firmware is indeed the first thing to do. That firmware also has the YotaStore to check out the extra applications you can install. You can also find a few extra applications that are not in the YotaStore in this forum http://xdaforums.com/yotaphone-one/orig-development Have fun with your Yota! :)
[YotaPhone] The_Rusty_Geek:
Thanks for the tip! My phone is arriving on the 17th, I look forward to its arrival.
[Android Q&A, Help & Troubleshooting] Deleted member 7858582:
I have an "old" Huawei Ascend G730-U10 which has a terrible..... TERRIBLE stock ROM, starting from the general stability of applications and the system itself to the fact that this phone was released to be never, ever updated; so I want to install a custom ROM.

But since I'm doing it, there are over 9000 bugs and problems, and maybe the only thing that went almost right was rooting (except for the fact that I'm stuck with KingRoot since SuperSU refuses to install).

First of all, I couldn't even request the unlock code the usual way, since the code to bring up the Product ID didn't work and I had to contact Huawei directly.

After getting the code, I booted into the bootloader, did "fastboot oem unlock *code*" and... I don't even know if it worked! No message appeared and doing "fastboot oem get-bootinfo" returns "FAILED (remote: not support on security)".

After finding both a TWRP and a Clockworkmod build for this phone (the latter one is actually for G730-U00, I don't know if it would work), I tried doing "fastboot boot *path_to_recovery_image*", but that doesn't work either, as it just hangs on "downloading 'boot.img'..." without doing anything (last try I left it there for 20 minutes). I don't want to already flash the recovery directly since I want to test if it works and I don't want to brick the phone.

Can someone help me?

Bootloader pictures (if it can help):
[Sony Xperia X Performance ROMs, Kernels, Recoverie] niaboc79:
Soooo, what are you waiting to do a system dump guys?

If you're running the beta, enable usb debugging in developers options then pull system using adb.

adb pull /system

Thanks

EDIT:

Thanks [MENTION=3774707]sfkaudi[/MENTION] here's the system dump: http://xdaforums.com/showpost.php?p=69666564&postcount=20

Envoyé de mon F8331 en utilisant Tapatalk
[Sony Xperia X Performance ROMs, Kernels, Recoverie] wolfmannight:
[MENTION=599722]niaboc79[/MENTION] lol..... that's what i am waiting for..... thanks you explain it very well....

I searched 100+ forums and hosting sites with different different search queries , but still not found any person who hosted a dump...

I also replied in many threads... "plz pull out and share need for development" .... but feel like people updated their phones and went on mars... hahaha...
[Sony Xperia X Performance ROMs, Kernels, Recoverie] sfkaudi:
How to type the command
[Sony Xperia X Performance ROMs, Kernels, Recoverie] wolfmannight:
Download adb binaries and locate to that folder open command prompt by right click while holding shift key. And type above command in cmd.
[Sony Xperia X Performance ROMs, Kernels, Recoverie] sfkaudi:
Okay I will try to do this when i come back from the work
[Sony Xperia X Performance ROMs, Kernels, Recoverie] wolfmannight:
ADB installation guide: http://xdaforums.com/showthread.php?t=2588979
[Sony Xperia X Performance ROMs, Kernels, Recoverie] sfkaudi:
This is what happens.

What do I do wrong
[Sony Xperia X Performance ROMs, Kernels, Recoverie] wolfmannight:
Don't type: adb shell

Just only type :

adb pull /system
[Sony Xperia X Performance ROMs, Kernels, Recoverie] sfkaudi:
Did that in first place. But it was the same
[Sony Xperia X Performance ROMs, Kernels, Recoverie] sfkaudi:
This is what happens with add pull/system
[Sony Xperia X Performance ROMs, Kernels, Recoverie] niaboc79:
Does adb logcat works? Have you enabled usb debugging?

Envoyé de mon F8331 en utilisant Tapatalk
[Sony Xperia X Performance ROMs, Kernels, Recoverie] sfkaudi:
usb debugging enabled, yes

Logcat! Is this all what it writes?

I'll take a look when I'm coming home in the morning

I'm at work now

But as I remember

There was something not presented, system or some like that
[Sony Xperia X Performance ROMs, Kernels, Recoverie] zombiej79:
You have to issue pull command for each folder just pulling /system will give error so just reissue for each folder in system and it will work
[Sony Xperia X Performance ROMs, Kernels, Recoverie] wolfmannight:
Screenshot shows help info because of you miss typed command

adb pull/system :: its wrong

adb{space}pull{space}/system = adb pull /system

i cant see what you typed so send screenshot of what you typed as command. don't show last portion.
[Sony Xperia X Performance ROMs, Kernels, Recoverie] sfkaudi:
Yay it's on the way[emoji13] [emoji13]

---------- Post added at 03:58 PM ---------- Previous post was at 03:57 PM ----------

When it's finish I need to know where to upload or to who

And how
[Sony Xperia X Performance ROMs, Kernels, Recoverie] sfkaudi:
It's a nice view here from mars[emoji15] [emoji41] [emoji12] [emoji1]
[Sony Xperia X Performance ROMs, Kernels, Recoverie] wolfmannight:
zip "system" folder which is in same folder which contains adb.exe

And best way is use google drive for upload.

---------- Post added at 05:12 PM ---------- Previous post was at 05:11 PM ----------

lol
[Sony Xperia X Performance ROMs, Kernels, Recoverie] sfkaudi:
After zip (7zip), the size it is 1.7-8 gigs

Is that correct

It contains all the folders inside
[Sony Xperia X Performance ROMs, Kernels, Recoverie] wolfmannight:
Yup
[Sony Xperia X Performance ROMs, Kernels, Recoverie] sfkaudi:
beta zip system dump

hope it`s correct made

but here it is:D

https://drive.google.com/file/d/0B73hpXN7HGn8Y1JoOHc2UnlHekU/view?usp=sharing
[Sony Xperia X Performance ROMs, Kernels, Recoverie] :
Thanks
[Sony Xperia X Performance ROMs, Kernels, Recoverie] sfkaudi:
I say thanks for all your help

Niaboc79 and wolfmannight
[Sony Xperia X Performance ROMs, Kernels, Recoverie] sfkaudi:
Is it working (if someone has downloaded it)
[Sony Xperia X Performance ROMs, Kernels, Recoverie] :
Yup working.... no error in extract and all files are good... Nicely done
[Sony Xperia X Performance ROMs, Kernels, Recoverie] wd121366:
my phone is f8132,can i use this rom?
[Sony Xperia X Performance ROMs, Kernels, Recoverie] niaboc79:
This is not a rom but a system dump. These are only some files coming from Android Nougat, many other things are needed to do a rom with the dump.

Envoyé de mon F8331 en utilisant Tapatalk
[Sony Xperia X Performance ROMs, Kernels, Recoverie] wd121366:
thank you
[Sony Xperia X Performance ROMs, Kernels, Recoverie] sfkaudi:
Hey niaboc79

How long time can it take to make it usefull, this dump
[Sony Xperia X Performance ROMs, Kernels, Recoverie] Mazellat:
Is this Android Nougat / 7.0? http://xdaforums.com/xperia-x-performance/help/update-39-2-0-327-android-nougat-7-0-t3509385
[Sony Xperia X Performance ROMs, Kernels, Recoverie] Naphtha:
Hello is possible to have new dump with boot.mg? :p
[Sony Xperia X Performance ROMs, Kernels, Recoverie] niaboc79:
Download the firmware with xperia firmware downloader.

Envoyé de mon F8331 en utilisant Tapatalk
[Sony Xperia X Performance ROMs, Kernels, Recoverie] udelgadochio:
Is there any way to install Nougat without losing Root?
[Sony Xperia X Performance ROMs, Kernels, Recoverie] KWOKSFUNG:
Sorry this is off-topic, but would u build your rom for X performance? Coz there's no custom rom for X performance so far, would appreciate if u could build one :)
[Sony Xperia X Performance ROMs, Kernels, Recoverie] gungsye:
this is system dump for to use on jtag ??
[Moto G4 Questions & Answers] superpascu:
Hi everyone,

Do you think It is possible to stop OTA notifications?

I dont feel like and update and I have to stop It everyday...

Thanks
[Moto G4 Questions & Answers] bfridman:
I have not tried this but see this post: http://xdaforums.com/showpost.php?p=69535531&postcount=493

I do the temporary workaround by force stopping the Motorola Update service after every reboot. Go to Settings -> Apps -> "..." -> "Show system" -> select "Motorola Update Services" -> "FORCE STOP"
[Moto G4 Questions & Answers] superpascu:
Thank you very much!
[Moto G4 Questions & Answers] MrAlester:
Before I forced stopped "Motorola Update Services" my G4 kept crashing and having problems ever since it asked me to update. Now it's playing nice again. Thank you.
[Moto G4 Questions & Answers] rael75:
freeze motrola update services with titanium
[Moto G4 Questions & Answers] bfridman:
Is it correct that you need root for that approach? Some of us do not have that with the Amazon version of the device
[Moto G4 Questions & Answers] rael75:
ye sorry thought you was rooted
[Moto G4 Questions & Answers] libralibra:
It is annoying to me as well. If I stop the update service, can I still get Android 7 as the rumor said it's on the way to moto g4?

For the time being, I just set the time to be next 24 hours. So I only need to click that once everyday.
[Moto G4 Questions & Answers] bfridman:
I'm not sure. It may depend how you disable it. The temp method resets on reboot. The "perm" method can supposedly be undone with a similar command also you might be able to manually check by going to setting and checking for update but I'm not sure if someone has tried it. Which method are you talking about?