yashsingh1/xdaforums huggingface dataset:
[Meizu MX] weichieh007:
This may sound silly but my phone is already on flyme os 6.1.0.OG. Will flashing this zip with flashify enable me to install other custom ROMs (cynogenmod, mokee)? I have exhausted every effort to unlock the MX4's bootloader because it seems impossible for me to downgrade the international device to 4.2.8.2A to use the apk unlock. I'm also trying my hardest to avoid bricking my device. Any advice would be very much appreciated. Thanks :)
[Meizu MX] disnomia:
This roms is only for flashing with custom recovery(twrp), unlocked bootloader.

Trying this roms on official rom it will brick your device.

If you try to downgrade from official 6.1.0.0G to 4.2.8.2A from flashify better try from stock recovery.
[Meizu MX] weichieh007:
Yeah, I tried using stock recovery to downgrade to 4.2.8.2A but I always get 'Firmware Corrupt' no matter how many times I re-download from different websites. I've even tried going to 4.0.4I before going to 4.2.8.2A but I even got the same 'Firmware Corrupt' message in the stock recovery for the 404I downgrade process.

I've tried these urls:

http://download.meizu.com/Firmware/Flyme/MX4/4.2.8.2/cn/20150422020016/09eb1341/update.zip

http://downloads.meizufans.eu/mx4/firmware/stable/4.2.8.2/a/update.zip

Is this because international version mx4 can't be upgrade or downgrade to 'A' version? Or Android Lolipop roms can't be downgrade to kitkat roms? Please share your thoughts. Thanks :)
[Meizu MX] disnomia:
Try to downgrade to 4.0.4i and then upgrade to 4.2.8.2A and hope this will be the trick.

https://downloads.meizufans.org/mx4/firmware/stable/4.0.4/i/
[Meizu MX] wojted:
First try do downgrade to 4.5.7I and then downgrade to 4.0.4I and then upgrade to 4.2.8.2A.

Wysłane z mojego MX4 przy użyciu Tapatalka
[Meizu MX] weichieh007:
Thanks. I'll give it a try and report back.
[Meizu MX] weichieh007:
OMG! I managed to go to 4.0.4I via 4.5.7I as advised by [MENTION=2737098]wojted[/MENTION]. Now attempting to go to the mother of all bootunlocking roms - 4.2.8.2A!

Wish me luck!
[Meizu MX] weichieh007:
Success! Managed to upgrade to 4.2.8.2A from 4.0.4I. Had the bootloader unlocked and successfully flashed a custom recovery twrp. Now on cyanogenmod 12.1. Thanks to [MENTION=3601101]disnomia[/MENTION] and [MENTION=2737098]wojted[/MENTION] for the guidance!

But now that I'm on cm 12.1, I'm faced with another issue but that's for another thread.
[Meizu MX] Falnhir:
I currently have TWRP. Do you think that flashing the stock recovery to upgrade normally my phone to 6.1.0.1A with the update file from meizu is a good idea or it will brick my phone and loose any hope of reviving it with a backup?
[Meizu MX] weichieh007:
All I know is getting your device to 4.2.8.2A, root and unlock the bootloader with the above apk is a vital before flashing custom ROMs. Good luck
[Meizu MX] Falnhir:
Thanks for your quick answer but it seems to be quite complicated... I don't really have time for it... Isn't there any easier way to simply upgrade my phone to Flyme 6.1.0.1A? By the way, I lost the stock recovery img of my MX4, that's why i couldn't do the upgrade before...
[Meizu MX] wojted:
.You can not flashing the original Flyme from Meizu in twrp recovery.

Wysłane z mojego MX4 przy użyciu Tapatalka
[Meizu MX] Falnhir:
Yeah I know I meant flashing the stock recovery and then flash the normal Flyme
[Meizu MX] wojted:
If you flashing stock recovery using Flashify it does not, you should have no problem flashing stock Flyme. However, the first flashing Flyme 4.2.8.2A and after Flyme 6.

Wysłane z mojego MX4 przy użyciu Tapatalka
[Meizu MX] disnomia:
Here is the stock unpatched recovery for mx4

https://mega.nz/#!uh9VTYZT!CiXwYWCrgCbLS_jOEYa-LiiN7wWjDTHFHiVnsCWMxb8

Flash with flashify but first place the rom 4.2.8.2a(update.zip) to the device that you will need after
[Meizu MX] Falnhir:
Okay thanks again for your answer :)

How should I go back to 4.2.8.2A?

---------- Post added at 11:13 PM ---------- Previous post was at 11:06 PM ----------

[/COLOR]

Ok thank you again disnomia :) but isn't there any risk of flashing issue (like bootloop) that I couldn't fix without my TWRP backup since TWRP won't be installed as recovery? Or is the downgrade/upgrade safe?
[Meizu MX] disnomia:
It will be like when you buy the phone with stock recovery official rom and upgrade from ota work ok

but please if you dodnt know very well what you will do , think twice

this phone is like fire, playing a lot with fire at the end you will get burn if you dont know what you are doing.
[Meizu MX] Falnhir:
I'll be careful, at least I'll try, but anyway my battery is dead so I dont really mind as I know that I will have to buy a new phone by the end of the year...

So you are saying that I shouldn't flash the stock recovery and directely upgrade to official flyme 6? Why should I go back to 4.2.8.2A?

I didn't know the the MX4 was more "dangerous" than other phones, I had no big issues so far...

But as always thanks for your advices :)
[Meizu MX] disnomia:
I dont know about flyme 6 try for sure to go back to 4.2.8.2A and then you can update by air

About mx4 if you make any mistake the bootloader get locked and you cant do nothing to make it work again (or change motherboard)

If you search the mx forum to many threats about mx4 bricked phones
[Meizu MX] wojted:
[MENTION=3601101]disnomia[/MENTION] When can we expect Flyme 6.2.0.0A for TWRP? Is it possible somewhere available?
[Meizu MX] disnomia:
I try once but It give me errors when try to install

it has some extra files "lk.bin" and "recovery.fstab"

which I dont know what to do with them and afraid not to brick the phone so I give up
[Meizu MX] wojted:
Ok. Be careful. If there is a risk then don't do it.

Meizu MX4
[Meizu MX] disnomia:
6.2.0.0G_twrp

Thanks to "slavakrsk"

http://4pda.ru/forum/index.php?showtopic=689760&st=6600

I use this gapps 5.1_pico works ok

https://mega.nz/#!3s03VT4D!dlSHY1cSG3DgyLeosVkCforvhTtHwCSt_yH7C1Gw0n8

and this time install magisk 15.2 for root and works also fine

https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

(when finish and press reboot in recovery do not install root when ask for)
[Meizu MX] wojted:
[MENTION=3601101]disnomia[/MENTION] You are great! Thank You!
[Fire Q&A, Help & Troubleshooting] madxxcow:
Hello,

I have a KFFOWI which I rooted some months ago with Superjunky tool, and it worked great. Recently I lost root following Supersu messy update. I tried today to restore root with Superjunky tool : King root rooted succesfully, then when it was time to install supersu and delete Supersu something went wrong, script maybe didn't have root access, well I don't know.

My device is now stuck at the Fire boot animation. I'm ready to restore a stock version, but how can I be sure of the one which was installed, as I don't want to restore a different version and hard brick ? Is there a way from recovery or bootloader to identify firmware version ?

Any help will be appreciated.
[Fire Q&A, Help & Troubleshooting] madxxcow:
Displaying logs under recovery, I think I identified version : 5.1.1
[Fire Q&A, Help & Troubleshooting] DB126:
5.1.1 likely references the underlying version of Android which FireOS and all custom ROMs for this device are built upon.

To be absolutely safe reload FireOS 5.3.1 which is the highest rootable build. Before doing that try a factory reset (clearing cache/data) from the recovery menu. Often does the trick.
[Fire Q&A, Help & Troubleshooting] madxxcow:
Thanks. Installed 5.3.1.

Then several attempts to root it with Supertool/King root, around 6 or 7.

Everything works great now.
[Google Pixel XL Guides, News, & Discussion] Mr.GrizzlyBear:
Greetings fellow nerds. How's it hangin'

Note to admin, I don't have permissions to create a dev thread. Your move broooh.

Uhhhh so this whole "Wah VZN and I couldn't buy a google pixel in full because I'm poor" has been getting on my nerves. I too can't afford an $900 phone and due to college, my credit history is a burden.

I want to start a discussion on the feasibility of literally opening up a phone, jamming some probes in and directly overwriting the chip to a generic bootloader/kernel.

Maybe you'd have to replace the chip and start with a blank slate, I dunno, but it's a frikkin' rock encased in refined dinosaur crap. How could the awesome might of electricity (in the form of merciless shock therapy) fail against a turd-encrusted sand-dollar? I don't think so.

I just made this account. Hope to see some naysayers in the morning at least telling me the idea is pointless and I'm an idiot so I don't waste my time.

Btw I don't mean zapping a chip, I just meant using one of those in-system programmers. This method could probably never be patched which is worth looking at as an exploit. AMiR?

Anyone notice that Verizon's latest commercial stars the protagonist of Silicon Valley? As if.
[Google Pixel XL Guides, News, & Discussion] Hell-Razor:
I kind of agree but the knife cuts both ways here. Us making posts about devs needing to try harder to unlock the bootloader may just be getting annoying. They know who they are and they may or may not be working on it. I would love to know somebody that knew how to do this or have an understanding of this. Even at the basic level I wish I knew where they even started.

The way I look at it, the bounty for unlocking the bootloader being ~2k isnt enough. This probably takes weeks to do. I would assume whoever figures out the exploits has an engineering degree from somewhere and understands how programming and exploitation works. They can probably make more money in a weeks time than what the bounty will ever be from this site.
[Google Pixel XL Guides, News, & Discussion] bobby janow:
It's not the bounty or the money. There is no reason to unlock the bootloader since the Google version is unlockable. And then a new update comes out and it's locked again. It's just pointless.
[Google Pixel XL Guides, News, & Discussion] pcriz:
:eek:
[Google Pixel XL Guides, News, & Discussion] gumbi2400:
I've said it before, and I'll say it again. The best bet for unlocking this, or any other phone, is to keep an eye on Linux kernel vulnerabilities. It's not a magic box, it's a small computer running modified Linux. The tricky bit is if a vuln is found, it will be patched. Is it work? Yes. Is it more effort than it's worth? Probably. Is it fun? If it's interesting to you, then yes!

I think in the end, if you look at it as a mystery or puzzle when trying to unlock your device, it can be fun. If you are wanting or needing extra functionality that requires root, then you should likely buy it direct from Google. In principle I don't like that it's locked, but in practice it doesn't matter too much. I totally understand people not being able to afford to drop the money up front, hell I'm one of em! At the same time though, there's nothing magic about "the devs." They're just people who found this stuff fascinating and decided to learn how to do it. Which means YOU can do it too! Only thing standing between you and an unlocked device is investment, either in money (a google phone), or in time (learn how these things work and try it yourself).

Ok this ended in me rambling a bit. Hopefully it made sense.
[Google Pixel XL Guides, News, & Discussion] bsmitty83:
Has anyone tried manually flashing an ota update through the stock recovery ? It Should pass signature verification from the locked bootloader right ? If so , couldn't there be a way to fake the signature , so a modified .zip could be flashed on a locked bootloader ?

IDK just asking since I got a Verizon version a week ago . Been on Nexus devices since the Galaxy Nexus . I am pretty upset at my ignorance on not knowing Verizon locked the bootloader on their version before buying.

I'm not an expert but I have some experience modding kernels and recoveries on the Galaxy Nexus and Nexus 6
[Google Pixel XL Guides, News, & Discussion] bsmitty83:
Basically what I was getting at is there might be a way to trick the locked bootloader into thinking a .zip file I flash is an ota update when it's really something else . It's the only way I see a route into gaining superuser privilege.

Also I am going to call Verizon and see why they decided to do this. I can't see an answer that they could give that would be reasonable . Hopefully they have the ability to unlock them or push an update to unlock after the pixel 2 is out IDK .
[Google Pixel XL Guides, News, & Discussion] mattwheat:
You do that. Let us know what they say. It's prolly just a mistake on their part. They prolly didn't mean to lock them.

LMAO.
[Google Pixel XL Guides, News, & Discussion] jmc2543:
Id say save your time calling them. They will more than likely give you some ,in their eyes common sense, reasons in the direction of "Its network security" or "we don't want our customers unknowingly flashing a file not meant for the device and bricking their device" ect. Look online as to why they chose to lock the boot loader, because they can get away with it hiding behind network security and watching out for customers.
[Google Pixel XL Guides, News, & Discussion] pcriz:
I highly doubt it. They do it for security as well as a control measure when it comes to warranty, returns, and insurance.

You have dishonest people that would do things to their devices and brick them and try to say it's a defect. Back in the day you could load iPhone firmware onto an iPod, brick it so bad their in-store software tools couldn't find the root cause and walk out with a shiny new device because it looks like a defect.

The fact that a nexus / pixel is almost impossible to brick is irrelevant because they arent in the business of quantifying how brickable or not a device is and applying bootloaders accordingly.

The majority of their customers don't even know what a bootloader is.

Further more I don't think anyone in their 3 tier service model will give you a useful answer based off of the point above. Even if you got an answer how will that change what the current situation is.

Frankly I'd figure out a way to buy from Google and screw the run around because I bet you there are people holding out hope for an early exploit like we had on the Pixel which is highly unlikely.

Unless you can find how bootloaders are in violation of the block C rules, this is a losing battle.
[Google Pixel XL Guides, News, & Discussion] bsmitty83:
It's definitely not a security issue , if they were worried about it on their end , the network end , I would never have been running unlocked bootloader devices on their network for better part of a decade. There's no reason they can give other than " we don't want people messing with their phone "

I honestly don't care if they hang up on me when I call , but they greyed out a switch and left a message to contact them so that's what I'll do since I guess no one else ever has . I'll laugh if they do unlock it for me ......

Again I was merely trying to suggest ways to attack the problem , I'm surprised there isn't more of a will to over come the problem simply because it's a challenge , not go buy a google version . I did buy a google version , screw Verizon . I'll find a way to unlock it or someone who can , or they will .

Xda has changed a lot..... [emoji53]
[Google Pixel XL Guides, News, & Discussion] pcriz:
Them allowing you to run an unlocked device has nothing to do with what they sell. They can't prevent you from using a compatible device if their network supports it and it isn't black listed. That's an FCC rule, plain and simple. Has nothing to do with the bootloader on your device.

XDA hasn't changed, the fact that you think this battle is brand new and we are blazing a trail just shows a short sightedness of the community.

There have been hundreds of petitions created, there have been pushes in various device threads to flood the FCC with requests to elevate the issue. Verizon as well as other carriers have literally had lawsuits levied against them. This has literally been going on for YEARS.

Please tell me after reading all that what calling and wasting the time of tech support is gonna do.

The real funny thing is someone that thinks they can call tech support and simply get your bootloader unlocked. That is hilarious.

Tell me who do you think designed and very likely has the means to unlock the boot loader on your GOOGLE Pixel? Hint, it isn't Verizon.

Verizon didn't develop the patch that blocked the exploit either. So what do you really think Verizon is gonna do to help you by calling tech support.

You want your bootloader unlocked? Get super friendly with a Google Android engineer, get super smart with Android period, or get a lawyer.

Xda hasn't changed, the mobile market has changed and it is making it harder to feel bad for people that buy subsidized carrier phones and then cry about locked bootloaders

Especially when affordable unlocked devices exist. But hey, screw logic. Let's go harass CSRs like their jobs don't suck enough.
[Google Pixel XL Guides, News, & Discussion] bsmitty83:
I guess I wasn't being clear enough . All I was trying to understand is why its locked in the first place . My Nexus 6 was never locked by Verizon . What if I paid full price outright for it from Verizon ? Why would they care what I do with the phone once its paid for ? What would be the difference if I bought it from google and put a Verizon sim card in it ? You sound so keen on defending the company and their poor hapless CSR's lol .

I don't care about the petitions or any of what your telling me .

I have no interest in lawsuits , simply finding a means to unlock my bootloader .

I could care less if it was htc that designed the patch , or google or apple.

I'm looking to find a way to make it work because it's something to do .

It's about unlocking it , that's it . People on this site used to be about finding solutions to problems , that's all .

Tell me what's wrong with that logic.
[Google Pixel XL Guides, News, & Discussion] pcriz:
So you don't care about fighting the market status quo of carriers locking devices which would be a preventative measure to help all mobile device users. Got it...

You want to know why it's locked and how to unlock it, but can't trouble yourself with asking questions to the right people. Got it..

Part of solution finding is narrowing down all the efforts that have failed or won't work for obvious reason, like calling them and saying why is my phone bootloader locked, calling them and asking if they can unlock it. Yet the fact that I don't agree with that means there is inherently something wrong with XDA.

I mention legal means as it relates to their block c spectrum purchase, you don't want to hear that. Again let me say again you have to make comment that XDA has changed. But yet another path ignored.

I get it now so I will agree to disagree, some people want thumbs up and yes men around them instead of well rounded opinions.

I tell you what. If you call and they tell you how to unlock your device I will Google wallet you 50 bucks.
[Google Pixel XL Guides, News, & Discussion] bsmitty83:
I'm not interested in fighting the status quo , no .

I'm into actual software development . Hands on stuff . I'm not a politician .

Your trying to give me solutions to a problem that isn't relevant to my immediate problem. I was looking for software related fixes .

Your too hung up on me calling Verizon lol . It was more tongue in cheek than anything , and it was an edit to my post about finding a workaround to the greyed out settings switch . That was all .

So again if you have any advice on how to unlock the bootloader , which is what I'm trying to do , not fight the man , please advise .

That's the spirit of xda , software development , not "fighting market status quo"
[Google Pixel XL Guides, News, & Discussion] stinger4321:
So what did Verizon say?
[Google Pixel XL Guides, News, & Discussion] micmars:
My understanding is that Verizon suggested multi-pronged approach, including,

1. Call VZW customer service

2. Hire a lawyer

3. Complain to the FCC independent of your attorney

4. Start a thread on xda

4.1. Generically denigrate the quality and state of development on xda

4.2. Misspell "you're" as often as you please

4.3. Kvetch at xda users, including [MENTION=1164081]pcriz[/MENTION]

5. "Thank you for calling Verizon"

I believe that buying directly from Google was never mentioned.

Lol®
[Google Pixel XL Guides, News, & Discussion] pcriz:
Lol
[Google Pixel XL Guides, News, & Discussion] stinger4321:
Lol.. i figured he hadn't called yet.. just liked blowing smoke in here...But I did unlock my bootloader.... Sold it on swappa... Now waiting on pixel prices to drop or waiting for pixel 2.. meantime rocking my nexus 6 which has more support then the pixel...
[Google Pixel XL Guides, News, & Discussion] awakenedwithin:
I've called Verizon on the locked bootloader issue when I was stuck on O beta and trying to downgrade. I first called Google because I unenrolled the beta and never got the OTA to go back to 7.1.2. They told me to flash the image but I told them I couldn't since the bl is locked. The rep told me to call VZW to have them unlock it so I called them and the VZW rep was all "wut, we don't fool around with OS, call Google and tell them to unlock it." I called Google and was told they couldn't unlock it. I seriously miss root.
[Google Pixel XL Guides, News, & Discussion] bsmitty83:
Lol grammar police

Still waiting on someone to speak up with any contribution to unlocking the bootloader , besides finding grammatical errors in my posts . I believe that's all I was looking for , but no worries .
[Google Pixel XL Guides, News, & Discussion] bobby janow:
Only one thing. Verizon doesn't care about you or XDA users. They care about the corporate market. They want to sell phones to companies (multiple) with thousands (multiple) of users not a hundred here who complain about locked bootloaders. They can tell a company that their phones can't be rooted or modified to leak company documents due to root hacking and that the phones are locked down to prevent unauthorized use within said company.

So you are correct, buy a device from Google and use it on Verizon, that's fine by them. Because you're not a company buying devices but one lone wolf. This is about corporate sales and profits not whether or not you own the device. Their thoughts are if you don't like it then don't buy it. There will never be a bootloader unlock for the Verizon Pixel as it now stands. I'd venture to say the same with the Pixel 2.
[Google Pixel XL Guides, News, & Discussion] Akira Takamedo:
At the end of all of this between talking to Google and fighting with Verizon, at least I got to tell executive service how absolutely terrible Verizon was. As a former employee myself, screw em.

I would’ve left it alone finally but I think what set me off was that they said locking the bootloader ‘helps Verizon provide exemplary customer service’. That really pissed me off, because of course it’s unrelated but besides that Verizon is probably the worst, most anti-consumer carrier of them all.

It won’t mean anything but it felt good to vent.
[Google Pixel XL Guides, News, & Discussion] bobby janow:
You are correct. It doesn't mean anything to them. Don't let it get to you, just buy it from Google next time. Problem solved.
[Google Pixel XL Guides, News, & Discussion] Akira Takamedo:
Sucks because it was the only choice at the time, since the XL Black 128GB was out of stock forever through Google . At least I got pretty much the entire thing paid off when I brought it to my T-Mobile account with #GetOutOfTheRed after I ported that line out when Verizon decided to implement their forced throttling. Gave Verizon a second chance for a work line and all of this just reminded me why I originally ported out - while I still worked for them no less.

I’m more upset that Google allows Verizon to get their disgusting claws all over their product. I really doubt the Verizon deal benefitted sales all that much, and it makes Google appear weak for allowing what they do.