Related
I have been patiently waiting for the marshmallow upgrade on my ze551kl since I bought it last December, and hopefully soon it will get the official one since I see the 500 and 550 have received theirs. My questions are: should I try to unlock before the upgrade or, since I see nearly everyone having to downgrade in order to unlock, just wait to see if it will unlock under marshmallow?
2. I also see a lot of activity for the 550 for root and the firmware seems to be named the same, but are they really interchangeable since they are different chip sets? If the bootloader won't unlock, can I safely flash a prerooted 550 ROM on my 551kl? Thanks for any advice.
long2ski said:
I have been patiently waiting for the marshmallow upgrade on my ze551kl since I bought it last December, and hopefully soon it will Aget the official one since I see the 500 and 550 have received theirs. My questions are: should I try to unlock before the upgrade or, since I see nearly everyone having to downgrade in order to unlock, just wait to see if it will unlock under marshmallow?
2. I also see a lot of activity for the 550 for root and the firmware seems to be named the same, but are they really interchangeable since they are different chip sets? If the bootloader won't unlock, can I safely flash a prerooted 550 ROM on my 551kl? Thanks for any advice.
Click to expand...
Click to collapse
1. Unlocking before upgrading to MM is a safer option
2. You can flash ZE601KL's ROMs on ZE551KL and vice versa. You will find ZE601KL pre rooted stock ROM in shakalaca's mega drive. Link is in rajlko "working root for ze550kl" thread.
sziraqui said:
1. Unlocking before upgrading to MM is a safer option
2. You can flash ZE601KL's ROMs on ZE551KL and vice versa. You will find ZE601KL pre rooted stock ROM in shakalaca's mega drive. Link is in rajlko "working root for ze550kl" thread.
Click to expand...
Click to collapse
Thank you for the reply.
Does the 601 have a different pixel density that might give me problems?
long2ski said:
Thank you for the reply.
Does the 601 have a different pixel density that might give me problems?
Click to expand...
Click to collapse
There are no problems at all, both are Z00T. In fact asus uses the same ota for both. If there were any problems associated due to anything like pixel density, etc, I would have mentioned it, right? Go ahead and flash any ZE601KL ROM on ZE551KL. But never cross flash baseband, aboot etc. No Custom ROM contains baseband and other critical components, unless specified.
Hello
I am aware that there isn't any warranty at all here that anything you do won't have negative effects on your phone. I've flashed quite a few roms on phones like the oneplus one, sony xperia sp, samsung galaxy core plus, nexus 5x, lg cookie, moto defy plus,... I've had tens of soft bricks, but never anything I couldn't recover from.
Anyways, I'm sick and tired of the laggy MiFavor UI on this phone, and would like to install CM13. I've an A2016G. I've seen some EU folk have issues with Tenfar's unlocking method, having hard bricked them since they can't get into a certain (EDL?) mode.
My question is this: if I read every thread and follow every step very carefully, is there a major risk my axon 2016G turns into a 450 euro paperweight? Is there perhaps another unlock method that's 99% secure?
Thank you
Jan
Hate to be that guy, but is there no-one with some knowledge around this?
Thanks.
Controllerboy said:
Hate to be that guy, but is there no-one with some knowledge around this?
Thanks.
Click to expand...
Click to collapse
Let me be the second guy, I'm amazed no one replied...
I'm in the same predicament; do I stay stock and use a great piece of hardware with crap software, or do I dare take the plunch and be able to make the phone as it ought to be at the risk of ending up with a very expensive paperweight...
What the hell did ZTE think when developing the A2017G model. And why is there after all these month no clear answer/procedure for this model. Is it that rarely used? How come there is no solution even though the firehose files are out there?
Hope someone finds a fullproof solutions soon....
Cheerz,
/Cacti
Verstuurd vanaf mijn ZTE A2017G met Tapatalk
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
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.
lag?
Controllerboy said:
Hello
I am aware that there isn't any warranty at all here that anything you do won't have negative effects on your phone. I've flashed quite a few roms on phones like the oneplus one, sony xperia sp, samsung galaxy core plus, nexus 5x, lg cookie, moto defy plus,... I've had tens of soft bricks, but never anything I couldn't recover from.
Anyways, I'm sick and tired of the laggy MiFavor UI on this phone, and would like to install CM13. I've an A2016G. I've seen some EU folk have issues with Tenfar's unlocking method, having hard bricked them since they can't get into a certain (EDL?) mode.
My question is this: if I read every thread and follow every step very carefully, is there a major risk my axon 2016G turns into a 450 euro paperweight? Is there perhaps another unlock method that's 99% secure?
Thank you
Jan
Click to expand...
Click to collapse
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.
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.
Sent from my ZTE A2017 using Tapatalk
jawz101 said:
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
Click to expand...
Click to collapse
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.
Just unlocked mine working great.
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.
rendler said:
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.
Sent from my ZTE A2017 using Tapatalk
Click to expand...
Click to collapse
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..
keessonnema said:
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..
Click to expand...
Click to collapse
Yup, using Chinese model with 128GB of storage.
Sent from my ZTE A2017 using Tapatalk
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.
jawz101 said:
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
Click to expand...
Click to collapse
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.
rczrider said:
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.
Click to expand...
Click to collapse
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://forum.xda-developers.com/search.php?searchid=430010789
Here is tenfar's response to him
http://forum.xda-developers.com/axo...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
jawz101 said:
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://forum.xda-developers.com/search.php?searchid=430010789
Here is tenfar's response to him
http://forum.xda-developers.com/axo...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
Click to expand...
Click to collapse
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.
xtermmin said:
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.
Click to expand...
Click to collapse
Would that be this method?
http://forum.xda-developers.com/axon-7/how-to/bootloader-unlock-t3437778/page1
And thank you @peramikic 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.
jawz101 said:
Would that be this method?
http://forum.xda-developers.com/axon-7/how-to/bootloader-unlock-t3437778/page1
And thank you @peramikic 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.
Click to expand...
Click to collapse
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.
peramikic said:
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.
Click to expand...
Click to collapse
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
jawz101 said:
Would that be this method?
http://forum.xda-developers.com/axon-7/how-to/bootloader-unlock-t3437778/page1
Click to expand...
Click to collapse
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)
Hi all, I'm a US user with W09 and would like to get it to Nougat - I have read the entire "Update to EMUI 5.0" thread and there appeared to be several possible routes, but most were regarding the European version.
I have a US Wi-Fi model and have no allegiance in keeping it a US one, if there's a way to remove the regional aspect to gain access to the update (BETA or otherwise).
I would greatly appreciate if someone who has some experience with or is very confident of the correct path would shed some light for me.
Thank you!
Have you tried update via Firmware Finder? Witch firmware version do you have now?
Sent from my Nexus 6 using Tapatalk
33adi said:
Have you tried update via Firmware Finder? Witch firmware version do you have now?
Click to expand...
Click to collapse
I've just finished reading the entire thread linked above that mentions that method a number of times, so I'm certainly familiar with it, but haven't tried it because sprinkled throughout that thread are plenty of issues encountered. Also, there's no mention of US hardware/firmware specific instructions.
I'm on W09 as mentioned in the OP - thanks for the reply!
Install Firmware Finder from Playstore and post a screenshot with firmwares that appear there.
Sent from my Nexus 6 using Tapatalk
33adi said:
Install Firmware Finder from Playstore and post a screenshot with firmwares that appear there.
Click to expand...
Click to collapse
I'm away from my tablet at the moment but will do later on when I get home.
We will see after that what we can do. I have updated my tablet to Nougat, but I have BTV-DL09 (4G European version).
To change region I think you have to unlock bootloader.
Sent from my Nexus 6 using Tapatalk
33adi said:
We will see after that what we can do. I have updated my tablet to Nougat, but I have BTV-DL09 (4G European version).
To change region I think you have to unlock bootloader.
Click to expand...
Click to collapse
Here's what's in firmware finder @33adi
What's the advantage to switching from US to EU roms? I unlocked, rooted, enabled 5ghz band for wifi, and now only need nougurt but much like the original poster not sure the best route.
Sent from my BTV-W09 using Tapatalk
gaidin43 said:
What's the advantage to switching from US to EU roms? I unlocked, rooted, enabled 5ghz band for wifi, and now only need nougurt but much like the original poster not sure the best route.
Click to expand...
Click to collapse
The advantage of removing the US stock rom is that the European one has a beta available that is very stable. My thread is seeking someone who's confident of the steps to 1st going European & 2nd installing nougat once there, as there was some debate of complexity to doing even that.
I've been through exactly what you are wanting to do @dutchdoggs54 . Unfortunately I can't tell you step by step how I got to where I'm at.
I was on W09128BXXX out of the box . Read the topic that you have linked in your first post and decided to do it using firmware finder to force the update to Nougat as they described. It actually went very well and Nougat worked great with the exception of Bluetooth not working.
I have to say during the upgrade when it booted into recovery and it was TWRP I was concerned. Believe it had an error but it worked and replaced TWRP as I recall with a stock recovery.
So after all that I decided I wanted my tablet branded as a BTV-W09C100B006. Below is the topic where a member thought they bricked their tablet.
https://forum.xda-developers.com/mediapad-m3/how-to/bricked-m3-btv-w09-t3612699
They were given directions to download the Full update package for the version I just mentioned.
This member got their tablet working again and in the process found that 5Ghz wifi is enabled on C100B006 by default.
That was the main reason I rooted my tablet.
I followed the directions knowing I force install a different version of Nougat from your link.
Downloaded the full version software and dropped it in the dload folder on my US tablet and did the upgrade.
Tablet rebooted and shortly after it rebooted again going to recovery (I tried may times to boot). Don't recall the error but after I unlocked my bootloader again it reset the tablet and I was able to access it again. I did relock the bootloader so I can see updates without any problems after that.
In the end I got what I was after. My tablet shows as a BTV-W09C100B006 and can check for updates.
5Ghz wifi is enabled by default. As I said I relocked the bootloader so I'm not rooted. Overall it's works so well I'll wait for Nougat to get released and then do the official upgrade. After the scare of booting to recovery it was worth every nervous minute of it.
Try to talk to OP from this thread:
https://forum.xda-developers.com/p9/...-root-t3374068
Maybe he can make this app available to Mediapad M3, then changing OEMINFO will be easy.
I posted a question there.
No luck
Ok, so I tried following @Samavb's great instructions and guidance in the other thread last night. Made it all the way to the point where he says to install 009 from the Huawei website - got it downloaded and loaded up on the tablet only to find that it wouldn't install because the 009 file on the website is BTV-DL09 not the BTV-W09 version a US tablet would need.
So I got frustrated and tried installing the B301 build that appeared on firmware finder when I was on the W09-006 build...this was nougat and was cool but no keyboard and the play store wouldn't install anything, so I was forced to revert back to 006.
So, long story short, hours of work have confirmed that there doesn't appear to be a way to get a US tablet to fully functional Nougat at the moment. If there was a 009 or 010 build like Samavb mentions for the US model, maybe it would work, but those aren't anywhere to be found - firmware finder, russian site he mentions or otherwise.
So, I'll happily sit on 006 and wait for a US OTA update. That is unless anyone can tell me exactly how to make this US model into a European model.
Same boat as original poster. US w09 on build c128b003. Firmware finder just finds the same version. Anyone know when there might be a us version update released. I thought it was supposed to be may so have been waiting patiently.....but may is over.
dr_pepper said:
Same boat as original poster. US w09 on build c128b003. Firmware finder just finds the same version. Anyone know when there might be a us version update released. I thought it was supposed to be may so have been waiting patiently.....but may is over.
Click to expand...
Click to collapse
In Firmware Finder select the menu in the top left corner. (3 bars)
Right below your model number, select change model and enter BTV-W09C100 and then search.
You should see B301 and it's a full OTA. However, as I understand it this is just a beta/test release.
Only issue I had with it, bluetooth didn't work. Seeing as how I don't use it, didn't bother me.
I highly recommend you fall back to the other topic about forcing the upgrade to Nougat.
Only difference from my tablet and yours. I was on C128B002. I had already rooted and couldn't get that update.
Also US 64gb version here and hoping for an update to Nougat and EM5. Would love to see it!
Huawei have been quite attentive for updates in other markets which is great. Too bad the non-LTE version in US doesn't get the same love.
Buying this tablet was a roll of the dice for me, banking on the hope that Huawei would be attentive to software updates (for all markets) and custom ROMs could serve as back up/enjoyment. This tablet has solid hardware and with another launcher it is decent.
Sadly, my experiment to try out a non-Nexus device without the latest (or close to pure) Android version is coming to an end. The last M3 sold on Swappa went for around $300.
johninsf said:
Also US 64gb version here and hoping for an update to Nougat and EM5. Would love to see it!
Huawei have been quite attentive for updates in other markets which is great. Too bad the non-LTE version in US doesn't get the same love.
Buying this tablet was a roll of the dice for me, banking on the hope that Huawei would be attentive to software updates (for all markets) and custom ROMs could serve as back up/enjoyment. This tablet has solid hardware and with another launcher it is decent.
Sadly, my experiment to try out a non-Nexus device without the latest (or close to pure) Android version is coming to an end. The last M3 sold on Swappa went for around $300.
Click to expand...
Click to collapse
I just updated the firmware finder app and it now shows the full ota for nougat. It wasn't found until I updated the app.
purple lady said:
I just updated the firmware finder app and it now shows the full ota for nougat. It wasn't found until I updated the app.
Click to expand...
Click to collapse
Excellent and great news! Are you in the US and have the wifi only version?
johninsf said:
Excellent and great news! Are you in the US and have the wifi only version?
Click to expand...
Click to collapse
Yep.
Thanks Purple Lady!
Too anyone in this thread, I want to install the latest version available in Firmware Finder.
When I select download, I get 3 file choices. Which should I pick to download then what are the steps to update? Please point me to the best post to reference as there are a few.
johninsf said:
Thanks Purple Lady!
Too anyone in this thread, I want to install the latest version available in Firmware Finder.
When I select download, I get 3 file choices. Which should I pick to download then what are the steps to update? Please point me to the best post to reference as there are a few.
Click to expand...
Click to collapse
from what i gather. if you're going from MM to Nougat, you need to install the Full OTA. for that, there are 2 files, you will need both of them. from there, i'm not sure.
I was trying to get a more stable root this weekend. I decided I would flash back to stock, then re-apply SamPWND. Like an idiot, I flashed G950U1UEU2AQK2. The last 4 "AQK2" is the version of the firmware, and the "2" before that is bootloader version 2. After installing version 2, I cannot flash any old firmware, including the ENG firmware used for SamPWND!
Question 1: Am I out of luck? Time to sell this thing and buy a OP5T?
I was looking at some S8 teardowns, and the storage chip "Toshiba THGBF7G9L4LBATR 64 GB UFS (NAND flash + controller)" is a seperate chip from the MSM8998.
Hypothetically, if I could remove my UFS chip from the phone, and reprogram it, could I flash a custom bootloader?
This is a question for someone who knows more about the 835 than me. Does the chip verify bootloader using a signature stored on the board? is the UFS flash chip protecting itself from being overwritten, or is the upload code protecting from unsigned firmware?
or is Samsung's public key stored within the 835?
Thanks for the help.
tim.vrakas said:
I was trying to get a more stable root this weekend. I decided I would flash back to stock, then re-apply SamPWND. Like an idiot, I flashed G950U1UEU2AQK2. The last 4 "AQK2" is the version of the firmware, and the "2" before that is bootloader version 2. After installing version 2, I cannot flash any old firmware, including the ENG firmware used for SamPWND!
Question 1: Am I out of luck? Time to sell this thing and buy a OP5T?
I was looking at some S8 teardowns, and the storage chip "Toshiba THGBF7G9L4LBATR 64 GB UFS (NAND flash + controller)" is a seperate chip from the MSM8998.
Hypothetically, if I could remove my UFS chip from the phone, and reprogram it, could I flash a custom bootloader?
This is a question for someone who knows more about the 835 than me. Does the chip verify bootloader using a signature stored on the board? is the UFS flash chip protecting itself from being overwritten, or is the upload code protecting from unsigned firmware?
or is Samsung's public key stored within the 835?
Thanks for the help.
Click to expand...
Click to collapse
Bad news and good news...
Bad news first, there is no downgrading. Even if you raw programmed it wouldn't boot. There's no way to go back on that.
The good news...
The n8 v2 is rootable using samfail, and I see no reason that the s8 wouldnt too. I havent been able to work on it yet as I've been busy with my rom, but it's next on my Android Todo list.
If you'd like to guinea pig, since your already on U2 and have little to lose (only risk is soft brick) I'll let you know when it's ready
partcyborg said:
Bad news and good news...
Bad news first, there is no downgrading. Even if you raw programmed it wouldn't boot. There's no way to go back on that.
The good news...
The n8 v2 is rootable using samfail, and I see no reason that the s8 wouldnt too. I havent been able to work on it yet as I've been busy with my rom, but it's next on my Android Todo list.
If you'd like to guinea pig, since your already on U2 and have little to lose (only risk is soft brick) I'll let you know when it's ready
Click to expand...
Click to collapse
Oh yeah for sure! I was gonna just stick with touchwiz, but then I sent a message with those stupid emojiis and thats when it really got to me.
I will read up on SamFail. I can definitely handle flashing/recovery/etc. I've been trying to get more under the hood on these things.
Thanks
Tim
___EDIT____
I just tried PartCyborgRom and it shows the same error. Flashing the AP works (but throws the expected error). But on the boot loader flash, it has the same complaint about the boot loader version being less than the fused version.
I'm a little confused how this could work. The new version of the bootloader is resistant to installing any bootloader version less than 2, and that includes the engineering bootloader used by PartCyborgRom and SamPWND correct? I look forward to understanding the loophole.
Also, what exactly is contained in the "BL" package? is the "Download" interface part of the bootloader? Is the recovery interface part of the bootloader? The kernel (which is the boot.img?) is part of the AP, along with actual file system.
tim.vrakas said:
Oh yeah for sure! I was gonna just stick with touchwiz, but then I sent a message with those stupid emojiis and thats when it really got to me.
I will read up on SamFail. I can definitely handle flashing/recovery/etc. I've been trying to get more under the hood on these things.
Thanks
Tim
___EDIT____
I just tried PartCyborgRom and it shows the same error. Flashing the AP works (but throws the expected error). But on the boot loader flash, it has the same complaint about the boot loader version being less than the fused version.
I'm a little confused how this could work. The new version of the bootloader is resistant to installing any bootloader version less than 2, and that includes the engineering bootloader used by PartCyborgRom and SamPWND correct? I look forward to understanding the loophole.
Also, what exactly is contained in the "BL" package? is the "Download" interface part of the bootloader? Is the recovery interface part of the bootloader? The kernel (which is the boot.img?) is part of the AP, along with actual file system.
Click to expand...
Click to collapse
I meant I have to create samfail v2, not that you could flash the current. 1. Sorry that wasn't clear.
partcyborg said:
I meant I have to create samfail v2, not that you could flash the current. 1. Sorry that wasn't clear.
Click to expand...
Click to collapse
I knew it wasn't likely to work, I just thought I would go for it before bothering to set up my new TouchWiz Monster.
Also, is the telegram still up? The link on the SamFail for Note8 thread is expired...
Correct, I was only able to "upgrade" to BQK5 and now am running running Oreo 2ZQKO since there isn't much else to try So that might be something to do in the meantime
rudimenta said:
Correct, I was only able to "upgrade" to BQK5 and now am running running Oreo 2ZQKO since there isn't much else to try So that might be something to do in the meantime
Click to expand...
Click to collapse
There is a u1 (carrierless no bloat) rom that is on leave (the latest one). Updato has it
Am in the same situation, glad I read your post flashed the non carrier AQK2 and had been trying to root it, felt so silly,
I am also able to help guinea pig it =)
partcyborg said:
There is a u1 (carrierless no bloat) rom that is on leave (the latest one). Updato has it
Click to expand...
Click to collapse
That's the one I run before I went on to try oreo, which is actually running rather decent
Sent from my SM-G950U using Tapatalk
What custom recovery is there for Zenpad 3s 10 Lte Z500KL P00I?
How can it be rooted?
Dr.Ghobar said:
What custom recovery is there for Zenpad 3s 10 Lte Z500KL P00I?
How can it be rooted?
Click to expand...
Click to collapse
I haven't seen any. Custom recoveries other than twrp.
alecthenice said:
I haven't seen any. Custom recoveries other than twrp.
Click to expand...
Click to collapse
Where did you find twrp for Z500KL P00I ?
Dr.Ghobar said:
Where did you find twrp for Z500KL P00I ?
Click to expand...
Click to collapse
From what I gather from the thread the zm500 version of twrp also works for z500kl. I cannot confirm this but an individual there suggests it is possible as does the creator of this version of twrp.
and here I've hard time unlocking bootloader.. tried many unlocking apks.. none of them wants to install.
Hello, do you know if it can be rooted? I'd like to install the latest version of Android on my Z500KL...
Thank you.
I'm trying... I'stuck with magisk manager and patched boot.img without fastboot as it doesnt has unlocked bootloader... looking for a twrp to install boot.img but hard to find one.
Any news for this?
Nope
Any news for this? Trying to bypass google authentification, because forgot all credentials. Already have the firmware but need more info about TWRP for this model Asus ZenPad 3S 10 Z500K. Want to reinstall original firmware UL-ASUS_P00I-WW-5.4.6.0.
Nope they'll never allow bootloader unlock in this model.. and never update anymore I presume.. I think asus flashtool will help.. (I hope.)
any progress in this matter? would like to go for a custom rom,too
Just posted this on another thread about unlocking and custom ROM for this tab, hopefully I can get an answer here too and retire this tab if no progress.
#########
Looks like nothing has happened here in a while. Am hoping for an update though if some progress has been made. I can't even unlock the bootloader so far... never mind find a ROM that works on it!
The reason I'm here is, I now find that even the ASUS apps are no longer supported on Android 7 (not that I used the ASUS apps much), but still... I looked on the firmware page and was really saddened by the fact that the JP version (which I have) had only 4 months of support (ie date from first firmware and last firmware is only 4 months apart...). For the WW version, it was 6 months. This is really a complete joke... It's a real pity because the hardware is not bad at all, and it is one of the last 4:3 screen ratio tablets. It's terrible to think that this thing has not had even security updates for the last 5 years, so unless I can get a custom ROM on there, then I think I'm going to have to look elsewhere for something.