Search results

wouldn't be surprised if your posts provoked that

it is here... Treble is obviously not supported natively by this phone, and a couple of people made it work in a rather makeshift way, then took off, but even then the stuff we had been given by zte was incredibly broken. might have been different since zte had a deal with cyanogen to make cm13...

were they for arm64?

Did you give any consideration to what I said earlier? If your phone was actually locked we'd be back in square 1...

well it should work... Try booting into anything, you got either FTM or recovery with the key combinations. If you flash ANYTHING else your phone won't boot as it is locked, so DO NOT FLASH TWRP OR WHATEVER ELSE

uhh... i told you to use a nougat package ?

that's not what you have to flash lol Go to the EDL Tool thread (you can even find it by googling it, just to be sure it's made by djkuz) and download a package from there. You're flashing custom firmware on a phone that isn't even unlocked! Btw be sure that you're downloading one for your...

heh, at least you're on stock now? What ROM did you flash?

Then how did you attempt to unlock the phone? You need to get to fastboot and run that, usually what those edl packs do is just give you fastboot Sahara means DFU. If it says Sahara, then you're on DFU mode. You had to use the testpoint guide before, now you just can use EDL Tool directly or...

look. idk why you used the toolkit when you were suggested to use EDL Tool, but clearly that's on you, don't blame hamster for a mistake you made. We've been thinking about mass reporting it or something though, because i've been seeing bricks since it came out years ago... If I'm getting it...

the daughterboard, pretty much. I thought there might have been a reinforcement that came off or something unlikely like that

No, my description was a wiggling port. I don't even have fast charge since i don't have the original charger, i was using my qc3 charger and it barely uses 10w out of the 18w. Took it apart to see if I had to resolder or replace the port, and it was fine. after reassembling it was okay i miss...

Ello, I'm a temporary user having to put up with this thing... Came from an Axon7 which I shattered the screen of for the 2nd time, so a friend gave me his (mildly shattered touchscreen) honor 7x to use for now. i want to die honestly... Yesterday the usb cable started wiggling up and down and...

There's a package to flash TWRP's but it's way easier via edl tool since you just drop it on a folder and hit flash recovery If you installed the 9008 driver, it is very possible that Windows didn't find the dfu driver ("ZTE Handset Diagnostic Interface (DFU)") and installed the 9008 driver, so...

You might have the wrong drivers installed for the DFU mode. It sometimes happens. Try uninstalling them (try getting to dfu, then uninstall device - delete driver software for this device). after that, turn the phone off and then get into dfu again. It will probably install the dfu drivers, and...

Lacking info there, after bricking your phone what happened? Did it appear as "ZTE Handset Diagnostic Interface (DFU)"? In that case you just had to use MultiDL and then MiFlash. Sahara Mode is DFU, and the latest EDL Tool should get you out of it easily. So MiFlash worked? Did you fix the brick?

yep. By far the weirdest bug here.

Oki's fault - anyways not many people use Party, and the one swho did sometimes had non-working vendors even though they were correct. Still no. Our phone IS Treble now, hence the ROM has to be treble. The thing that has been "treblerized" is the Axon7. You can't take any ROM and "repackage"...

It does. Your partition is literally all wrong lol, should be System and 512. Not really - Treble is something inherent to the device, and on new devices, which have treble by default, everything is made to work with it. Think about it as a simple move of some files to a specific partition...

- creating vendor partion with TWRP w/PARTY mod. did you select 512mb and System? That's what you need to use. Anyways the best way would probably be installing LOS 16 as it makes you a vendor partition, but you'd have to delete the previous one for that. - flashing NFound v1.1 zip (vendor's?)...

It's not Google that has to fix Treble for it to work well on our phone; the problem is that our implementation of Treble is as makeshift as it gets... NFC is not a problem on GSIs though, you have to apply the simple fix and it won't misbehave. It's true though, GSIs use more RAM. Hardly a...

Did you have TWRP or anything else installed? If you don't have TWRP, install it via EDL with EDL Tool, then enter it and get stuff out via usb. You were most probably encrypted, in that case I honestly don't recall which TWRP handled stock encryption, but I guess the official one on twrp.me...

well it's not an axon 7. If you can't find a thread for it on XDA (extremely likely since Blades usually have zero dev scene) that's it. maybe try other forums.

did you do anything to the phone before? Battery change for example? I suspect your screen flex cable is bad, but since you could recover from it by turning it off and doing some voodoo magic, it kind of sounds like software... maybe just try one of the new device-specific Pie ROMs But yeah...

You two ever thought that it could be hardware? Maybe the antenna cable got disconnected?

lol. Try using Magisk, then get all of your stuff out of the SD card and format it. If your files aren't bigger than 4gb you can use fat32, otherwise try formatting it from the phone

well, as a start reading before doing anything dangerous is good... all of the bl lock guides should say that you cannot lock if you're not fully stock (stock recovery, stock system). First of all, the ZADIG driver is useless. It's only meant for axon7tool. Uninstall the device and tick...

i always just ask, why SuperSU? Don't use "Keep read only" on TWRP, that's useful when you have DM-verity enabled but SuperSU, Magisk, or the no verity zip disable that. I don't know if this is your problem but it might as well be. Also, issue "reboot disemmcwp" from the TWRP terminal or via...

From all the talk that I've seen about this, it seems that GPS doesn't work in LOS16 (maps will use cellular and known wi-fis for location). It does work on ViperOS Pie but with some bootstacks (B04 does the job, also seems like some B20 'stacks work). Maybe it's also dependent of the bootstack...

Do you format your data partition after every EDL flash? It will sometimes not boot, especially if it's in f2fs

lol. you could just straighten out the battery. in my case EDL flashes always failed when I did them without the battery. Black foil isn't adhesive, it's a cloth to protect the speakers, the adhesive thing is double sided tape on the edges. I just use cyanoacrylatenin tiny amounts and it works...

Lol, why is it in bad shape? If anything that's the perfect moment to do the copper coin mod (replace pink crappy goop with a pure enough polished copper shim sanded to size) What's the damage? did you scratch the grilles?

wrong section, this is a question... Check the guides to root. Marshmallow is easier to unlock but you can also use other EDL methods

Just EDL any version, like B12 now. Should work

well, if I'm being honest I have no idea, but i guess it has to do with the cache partition. Try flashing Nougat (B12 is fine) and also flash the latest official TWRP (from twrp.me, axon7 - you could probs use others but this one just works). Try holding Volume Up right before the phone boots...

That means DFU. If you uninstall the 9008 driver it SHOULD install the "ZTE Handset Diagnostic Interface" one (dfu driver) and then you would be able to use multidl or just edl tool directly, but if it's not doing so you could try two things: Uninstall the device, then unplug the phone. Find the...

Yes, I read that and thought (think) that you are trying to say that you SHOULD have something on the screen. EDL is completely black. And the LED won't turn on unless you are on DFU or something like that. Use EDL Tool and report back, MiFlash should flash even if the bootloader is locked

First of all DFU is not accessible with button combination unless you really bricked the phone. Power and vol- will get you to FTM (factory test) which has adb so it won't really be useful for anything in your situation. if the phone is bricked EDL will be replaced with DFU (power and both vol...

the battery has nothing to do with it. the display connector gets loose and does this all the time. Fortunately it never happened to me but i've seen more than 10 people with this problem here's a couple pics for ya, the best solution is to take it apart and secure it but if you never did it...

Making a vendor partition is not going to magically make the vendor contents for you. The partition might be created, but the actual vendor has many HALs and stuff like that, which is specific to your phone.

that's literally how edl looks, don't try to draw conclusions... Try uninstalling the Qualcomm 9008 driver (uninstall device, also tick delete driver software) and hold all 3 buttons of the phone until the led flashes and device manager refreshes. it should install the right driver (could be...

well there's a new build in the previous page. Not sure why you're using Lineage though, did you consider any GSI?

because it's not official anymore

yes, you can issue "su" then "dumpsys media.audio_flinger" from a terminal while playing hi-res stuff, then find the output that says "Processing: yes" and check the resolution

you know there's usually text right above the error code, right? That would be more than useful

to conclude this it was a simple bootstack problem

use the dfu tool (MultiDL, Raystef made a couple of threads about it), or try using EDL Tool, and if nothing works try opening the phone and unplugging the battery then plugging again and entering EDL, if THAT fails use my dfu unbrick guide (google "dfu unbrick", it should be the first result)

i'm sure it's there, look at the last option in the menu

well, he gave a pretty good hint there There's a certain software made by a certain person right above you, with the ability to fix that fukkup. It's in the "ROMs, development" section and it's called EDL Tool. Anyhow why can't you unlock it if it was your phone?? You just need to put your...

Are you in stock? I really don't know why you're getting this, it was very easy to fix a while ago... but now it seems that v4a doesn't play very nice with the latest gsi's