Related
Does anybody know what Samsung is doing about hardbrick issue ?
Latest news from Daniel Hillenbrand was on Jun 8 (He contacted Samsung and:
Patches will be out in form of new official ROMs and also sourcecode releases after testing, which might take some time
Click to expand...
Click to collapse
source: Daniel Hillenbrand Google +
Yesterday, Entropy512 said:
Even secure erase is not 100% guaranteed to cause damage. It turns out it will only cause damage when the eMMC is in a certain specific state. (I unfortunately can't elaborate on the specifics as that is proprietary information) - However it explains why some people manage to wipe even in CWM without damage.
Click to expand...
Click to collapse
I don’t want any details, but after reading all the threads, information from Ken Sumrall and posts on Samsung official support forums, I think that they don’t want to admit, that there’s a problem with their eMMC chips. I know that it is almost impossible to recreate brickbug situation on stock devices - so there is no problem for Samsung at all (custom rom - not their problem) .
I just don’t know what to think – Samsung is currently Rolling-out the Official ICS 4.0.4 Update for Galaxy S2 and we all know, that each of them contains unsecure kernel (all they need to do is disable emmc_cap_erase, right? )
I may be wrong, maybe fix is a lot more complex than just disabling emmc_cap_erase in kernel, but this is the difference between secure and unsecure kernel…so why they didn’t ? Everyone knows about eMMC bug, but Samsung is rolling out new updates and don’t care…
Its Simple They moved on .......
They dont want to spend their time and energy on this phone instead they are thinking about s4 or galaxy note 2
No, they are not. It's so simple to fix hardbrick bug... But Samsung is not interested at all, and seems that it's a computer working on the builds, not real people, since they still releasing this crap. Samsung super fail.
They just don't care and why should they?
The stock Firmwares are noobproof, but if some geeks from XDA D) flash custom Roms its already not their business because a usual customer never even get accidentally into a recovery where he could wipe the phone.
So, they say users fault. Why invest $$$ for a few people who already figured out themselves how to avoid that bug on an "old" device.
Business.Simple as that.
Testraindrop said:
They just don't care and why should they?
The stock Firmwares are noobproof, but if some geeks from XDA D) flash custom Roms its already not their business because a usual customer never even get accidentally into a recovery where he could wipe the phone.
So, they say users fault. Why invest $$$ for a few people who already figured out themselves how to avoid that bug on an "old" device.
Business.Simple as that.
Click to expand...
Click to collapse
Actually its also their loss as they fix the bricked devices under warranty
No one will tell "I flash a ROM from xda and bricked my phone" to the service center guys
Sent from the beast using CMX
I think there is a fix - I heard a couple XDA members saying that they've got a PIT file to fix the problem. Though all it does is make a new /data partition, and you lose a bit of your space (8GB instead of 11GB)
epic118 said:
I think there is a fix - I heard a couple XDA members saying that they've got a PIT file to fix the problem. Though all it does is make a new /data partition, and you lose a bit of your space (8GB instead of 11GB)
Click to expand...
Click to collapse
That's not a fix. Just a workaround to get the device up and running
Sent from my GT-I9100 using xda app-developers app
I talked with the Support to Sony, because the SGP321 formates every sdcard into the fat32 format
answer from sony:
In the LTE version is currently in effect so that only the FAT32 format is detected. But this should be changed in the future with an update.
so what can i do that other formats works?
cheers
yes pretty sad, I just got my tablet today after playing with it a few hours its pretty disappointing. Screen mirroring will disconnect wifi which make it pretty useless since i want to stream stuff online off my tablet thru Tv. Don't know if its sony's buggy software or hardware limitation. The os is pretty choppy compare to my note 2 and all this problem, wifi direct (can't transfer big files), no exfat, bad miracast support (wifi disconnect when in miracast mode), codec support pretty poor and no sub support, dunno what other problem i will find. Nice design but poor software should have stick with samsung poor design but better software right out of the box.
is theire a possibility to use xfat or nfts?
a script or so?
gerzii said:
I talked with the Support to Sony, because the SGP321 formates every sdcard into the fat32 format
answer from sony:
In the LTE version is currently in effect so that only the FAT32 format is detected. But this should be changed in the future with an update.
so what can i do that other formats works?
cheers
Click to expand...
Click to collapse
exFat works fine on my SGP311. It seems odd that it wouldn't work on the 321.
yes i know
but i thought it gives from someone a sctipz now? *hM*
You can use Paragon NTFS & HFS+ or USB OTG Helper to enable NTFS&exFAT support to SGP321.
Rootk1t said:
You can use Paragon NTFS & HFS+ or USB OTG Helper to enable NTFS&exFAT support to SGP321.
Click to expand...
Click to collapse
i will try and give u a feedback
Rootk1t said:
You can use Paragon NTFS & HFS+ or USB OTG Helper to enable NTFS&exFAT support to SGP321.
Click to expand...
Click to collapse
with paragon my tablet always reboots
and
with usb otg helper it doesnt find the sdcard
what i am doing wrong ?
gerzii said:
with paragon my tablet always reboots
and
with usb otg helper it doesnt find the sdcard
what i am doing wrong ?
Click to expand...
Click to collapse
both programs work, so you're definitely doing smth wrong.
Rootk1t said:
both programs work, so you're definitely doing smth wrong.
Click to expand...
Click to collapse
and what?
Hi all I'm using an app called "nexus media importer" it costs $4 and can let you browse your ntfs hdd
Any news on when this update will arrive?
I just bought the SGP321 version but am returning it since the main reason why i got it is to watch 1080p movies
Andreas1457 said:
Any news on when this update will arrive?
I just bought the SGP321 version but am returning it since the main reason why i got it is to watch 1080p movies
Click to expand...
Click to collapse
just root the tablet, install the fix and the app and it works
Won't there be a problem with the warranty after rooting the device? Will I still be able to get the firmware updates from sony? I'm not sure that I'm ready to do this when it's something that should be possible from the beginning.
Andreas1457 said:
Won't there be a problem with the warranty after rooting the device? Will I still be able to get the firmware updates from sony? I'm not sure that I'm ready to do this when it's something that should be possible from the beginning.
Click to expand...
Click to collapse
updates are be able to recieve
but with the warranty i dont know sorry
Andreas1457 said:
Won't there be a problem with the warranty after rooting the device? Will I still be able to get the firmware updates from sony? I'm not sure that I'm ready to do this when it's something that should be possible from the beginning.
Click to expand...
Click to collapse
Rooting won't affect your warranty, as it can be undone. What affects your warranty is unlocking the bootloader, which is something you do when you want to install a custom kernel, and an unlocked bootloader stays that way for good.
Shanliang- said:
Rooting won't affect your warranty, as it can be undone. What affects your warranty is unlocking the bootloader, which is something you do when you want to install a custom kernel, and an unlocked bootloader stays that way for good.
Click to expand...
Click to collapse
I understand, might just do that instead of returning it then. Is it safe to root the device and is the process simple? Can i update the device over the air just as i do with my unrooted galaxy s 3 phone?
Is unlocked bootloader the same as unrestricted concerning network operators? I have bought a version that works with all operators. Guess i don't need to unlock the bootloader and that i won't affect the warranty by rooting?
Thanks a lot for the help!
Andreas1457 said:
I understand, might just do that instead of returning it then. Is it safe to root the device and is the process simple? Can i update the device over the air just as i do with my unrooted galaxy s 3 phone?
Click to expand...
Click to collapse
You can keep getting OTA updates after you root the device. Rooting it is as simple as connecting the tablet to your computer via USB and executing a file in your PC.
For further instructions you can go to DooMLoRD's Rooting Kit.
Shanliang- said:
You can keep getting OTA updates after you root the device. Rooting it is as simple as connecting the tablet to your computer via USB and executing a file in your PC.
For further instructions you can go to DooMLoRD's Rooting Kit.
Click to expand...
Click to collapse
Thanks a lot! Is it as easy to unroot the device? Saw that the developer only wrote that he would post something about this later. I take it this doesn't unlock the bootloader?
Andreas1457 said:
Thanks a lot! Is it as easy to unroot the device? Saw that the developer only wrote that he would post something about this later. I take it this doesn't unlock the bootloader?
Click to expand...
Click to collapse
One way of unrooting is to flash a stock firmware using Flashtool. Stock firmwares can be found in the Development section, and for the Flashtool, Google will give you the link to get it. This procedore doesn't require unlocking the bootloader either.
What are the chances of the device getting rooted then? I noticed the GS4's bootloader was locked but it was able to be rooted. I don't need custom ROM's just root. Any answer would be appreciated.
Thanks!
Bump
I would say the chances are pretty good that root will be achieved. You will just have to wait till an exploit is found. You could do what I did and get the tmobile version which already has a custom recovery where you can flash a rooted stock rom.
mircury said:
I would say the chances are pretty good that root will be achieved. You will just have to wait till an exploit is found. You could do what I did and get the tmobile version which already has a custom recovery where you can flash a rooted stock rom.
Click to expand...
Click to collapse
Is the T-Mobile one has att LTE band ?
According to the FCC lab report, yes it does.
mircury said:
According to the FCC lab report, yes it does.
Click to expand...
Click to collapse
But there is no real world confirmation yet.
daraj said:
But there is no real world confirmation yet.
Click to expand...
Click to collapse
That is correct. No one knows for sure yet. All we know is that it has the correct radio and bands. Hopefully it will work the same as the S4.
After some more digging it looks like the write protection enabled only applies to the bootloaders and other lower level partitions, which means we might be able to flash the boot/recovery/modem partitions still. However, it WILL trip the Knox flags, which means the warranty is void and will NOT be able to run any Knox apps.
None of these things bother me since AT&T doesn't know about any of this stuff and Knox isn't useful to me.
designgears said:
After some more digging it looks like the write protection enabled only applies to the bootloaders and other lower level partitions, which means we might be able to flash the boot/recovery/modem partitions still. However, it WILL trip the Knox flags, which means the warranty is void and will NOT be able to run any Knox apps.
None of these things bother me since AT&T doesn't know about any of this stuff and Knox isn't useful to me.
Click to expand...
Click to collapse
Where you able to verify this using the att build? In other words, do u know for fact that the bootloader if locked?
daraj said:
Where you able to verify this using the att build? In other words, do u know for fact that the bootloader if locked?
Click to expand...
Click to collapse
As I stated in this thread;
http://forum.xda-developers.com/showthread.php?t=2458928
ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
WRITE PROTECTION: Enable
With that, even the Galaxy S3 shows QUALCOMM SECUREBOOT: ENABLE after it is unlocked, and WRITE PROTECTION: Enable applies to the bootloaders and other sensitive partitions.
I would assume we can flash boot/recovery/modem.
designgears said:
As I stated in this thread;
http://forum.xda-developers.com/showthread.php?t=2458928
ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
WRITE PROTECTION: Enable
With that, even the Galaxy S3 shows QUALCOMM SECUREBOOT: ENABLE after it is unlocked, and WRITE PROTECTION: Enable applies to the bootloaders and other sensitive partitions.
I would assume we can flash boot/recovery/modem.
Click to expand...
Click to collapse
Knox kernel thats new. We are screwed. Better off getting the Rogers/Tmobile version(most prbly wont be locked)
daraj said:
Knox kernel thats new. We are screwed. Better off getting the Rogers/Tmobile version(most prbly wont be locked)
Click to expand...
Click to collapse
Ya, it seems like the kernel is encrypted, I have been unable to rip it apart with any current methods.
So basically we can root the device but the possibility of flashing new ROMS and kernel's will be extremely difficult?
daraj said:
Knox kernel thats new. We are screwed. Better off getting the Rogers/Tmobile version(most prbly wont be locked)
Click to expand...
Click to collapse
Pikezer1337 said:
So basically we can root the device but the possibility of flashing new ROMS and kernel's will be extremely difficult?
Click to expand...
Click to collapse
Yup..if the old root exploit still works (if it does not, then pretty much toast). The bootloader *cannot* be replaced yet (even in S4), if you were lucky and had the earlier bootloader then you could "loki" run custom roms/recoveries. Otherwise the only option appears to be the "kexec" type method (safestrap), yuk..get one without a bootloader lock (hoping T-MO does not lock it and allows unsigned kernels and recoveries)..
Although I don't understand why ATT would this, the above methods for S4 has made people who didn't understand the process fully to go back to Samsung//BB service centers to reflash the stock f/w.
Pikezer1337 said:
So basically we can root the device but the possibility of flashing new ROMS and kernel's will be extremely difficult?
Click to expand...
Click to collapse
Actually getting root is going to be difficult. An unpatched exploit will be needed. Rom's and kernels will be the extremely difficult part. Samsung's credibility is on the line for a secure business solution with KNOX so you better believe they are going to make it hard if carrier's like ATT decide to lock down their devices like they have.
Yeah, I'm still just trying to understand why ATT is doing this. Hopefully the old root method works then, otherwise it is a deal breaker for me.
Pikezer1337 said:
Yeah, I'm still just trying to understand why ATT is doing this. Hopefully the old root method works then, otherwise it is a deal breaker for me.
Click to expand...
Click to collapse
Since we pretty much know that att version is bootloader locked(designgears confirmed) do we know If the tmobile version or the International version has this Knox kernel?
daraj said:
Since we pretty much know that att version is bootloader locked(designgears confirmed) do we know If the tmobile version or the International version has this Knox kernel?
Click to expand...
Click to collapse
I don't think it matters at this point. My understanding is that with the custom recovery already available you can flash a rom with root and with knox disabled. There is already a dev working on striping knox out in the dev section.
Geez, it's just hard imagining a phone like the Note 3 never having root access. But hey if that's what happens, I guess there's nothing you can do.
mircury said:
I don't think it matters at this point. My understanding is that with the custom recovery already available you can flash a rom with root and with knox disabled.
Click to expand...
Click to collapse
That's correct. If a bootloader is unlocked and you ODIN flash a custom recovery and install su and push super su. The kernel is not SELinux permissive, then we just need to wait for the source drop, compile a new kernel. The important thing is the bootloader unlock and knox security allowing unsigned kernels and recoveries. From the S4 T-MO thread it appears that the T-MO version allows that..so it will not be a big deal..ATT ones of course you are pretty much toast.
I saw there's an unofficial Cyanogenmod rom out for the Axon 7 and was wondering if there if one available for the Mini (or if the Axon 7 version will work on the Mini)?
No and no. First we need a bootloader unlock to install custom roms. Till now ZTE doesn't offer a bootloader unlock for the axon 7 mini.
I am also very interested in this and hope that soon there will be something
There is a new tool for the Axon7. Mainly for backup and writing the recovery and boot partition.
There might be some hope for the mini.
Read what I wrote about it in the thread and try the "read" feature.
http://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
That sounds so great. I will try that at the weekend. Thank you for the information @celoxocis .
Senaxo said:
That sounds so great. I will try that at the weekend. Thank you for the information @celoxocis .
Click to expand...
Click to collapse
Let us know how t goes. I'm curious about if you at least read the boot and recovery using the tool.
It would mean the programmer was signed with the same key as for the Axon 7. I kinda doubt it because of the different SoC but you never know.
I'm on b21 and activated developer options for the first time, you can unlock the bootloader with a toggle of a switch, so maybe hope for a custom ROM?
fallen00sniper said:
I'm on b21 and activated developer options for the first time, you can unlock the bootloader with a toggle of a switch, so maybe hope for a custom ROM?
Click to expand...
Click to collapse
Unfortunately that switch doesn't work. (At least on b12 I haven't tried b21 yet) I asked ZTE and they said that it was left over from their Chinese version of their ROM, and that they aren't "allowed" to have it work on the US model.
holybabel said:
No and no. First we need a bootloader unlock to install custom roms. Till now ZTE doesn't offer a bootloader unlock for the axon 7 mini.
Click to expand...
Click to collapse
Apparently it works now, I am also posting on the ZTE forum and it allows adb commands from what was said, come on XDA I need root
Re: [UPDATE] Axon 7 Mini B2017G "Build 21" (US Version)
musicdjm Champion Jan 17, 2017 7:54 AM
fallen00sniper the option in the setting doesnt allow you to root the device, it is simply for ADB (commands through usb port) at this current time I have not seen any post on XDA or else where about anyone who has successfully rooted or unlocked the Mini yet. XDA would definitely be the best place to keep an eye out on that though.
https://forum.xda-developers.com/axon-7-mini
Nevermind, they said it doesn't do anything after saying it does.
fallen00sniper said:
Apparently it works now, I am also posting on the ZTE forum and it allows adb commands from what was said, come on XDA I need root
Re: [UPDATE] Axon 7 Mini B2017G "Build 21" (US Version)
musicdjm Champion Jan 17, 2017 7:54 AM
fallen00sniper the option in the setting doesnt allow you to root the device, it is simply for ADB (commands through usb port) at this current time I have not seen any post on XDA or else where about anyone who has successfully rooted or unlocked the Mini yet. XDA would definitely be the best place to keep an eye out on that though.
https://forum.xda-developers.com/axon-7-mini
Nevermind, they said it doesn't do anything after saying it does.
Click to expand...
Click to collapse
Has no one tried the above mentioned tool?
Like said it can't hurt as long as you use the "read only" commands.
Is this root method not legit?
http://rootoreviews.com/root-ZTE-Axon-7-mini-install-twrp-custom-recovery
No it's not. It already fails at step 1. Downloading TWRP. There ist no TWRP for the Axon 7 mini.
Hello, ¿Any news about rooting this terminal?
Thanks
Hello,I asked ZTE about unlockoing the bootloader or rooting the terminal and this is what they answered me (google made translation):
Good afternoon,
In response to your request we will advise you that in order to enjoy the manufacturer's official warranty we must cover critical configuration options that can be modified and lead to a malfunction of the terminal.
ZTE does not guarantee the correct functioning of your terminal if you unlock bootloader; Task that we discourage. In fact, should such an unlocking be detected, our official guarantee would be invalid.
Greetings,
No hope for us at the moment.
agmvc5 said:
Hello,I asked ZTE about unlockoing the bootloader or rooting the terminal and this is what they answered me (google made translation):
Good afternoon,
In response to your request we will advise you that in order to enjoy the manufacturer's official warranty we must cover critical configuration options that can be modified and lead to a malfunction of the terminal.
ZTE does not guarantee the correct functioning of your terminal if you unlock bootloader; Task that we discourage. In fact, should such an unlocking be detected, our official guarantee would be invalid.
Greetings,
No hope for us at the moment.
Click to expand...
Click to collapse
You'll get hope if I'm able to get my hands on one. For now, you all will have to wait. Just don't give up on it if you're looking for custom Roms. It should get the same treatment as the Axon 7.
Sent from my ZTE A2017U using Tapatalk
Core2idiot said:
Unfortunately that switch doesn't work. (At least on b12 I haven't tried b21 yet) I asked ZTE and they said that it was left over from their Chinese version of their ROM, and that they aren't "allowed" to have it work on the US model.
Click to expand...
Click to collapse
That doesn't make any sense. Why wouldn't it be "allowed" I came to this section of XDA to research which phone to buy, I guess I won't be "allowed" to buy this model, since the bootloader can't be unlocked. I know I maybe in the minority, but I still vote with my wallet. Moving along I guess....
OhioYJ said:
That doesn't make any sense. Why wouldn't it be "allowed" I came to this section of XDA to research which phone to buy, I guess I won't be "allowed" to buy this model, since the bootloader can't be unlocked. I know I maybe in the minority, but I still vote with my wallet. Moving along I guess....
Click to expand...
Click to collapse
I ended up returning my Axon 7 Mini after it had other issues (The speaker wasn't working with media audio) and got a Sony Xperia XZ and I love it, no regrets.
OhioYJ said:
That doesn't make any sense. Why wouldn't it be "allowed" I came to this section of XDA to research which phone to buy, I guess I won't be "allowed" to buy this model, since the bootloader can't be unlocked. I know I maybe in the minority, but I still vote with my wallet. Moving along I guess....
Click to expand...
Click to collapse
The bootloader will be unlocked, I can push for it now, but I decided to wait to N. If it's going to help users make a decision, I'll try and push for it now.
Sent from my ZTE A2017U using Tapatalk
Unjustified Dev said:
The bootloader will be unlocked, I can push for it now, but I decided to wait to N. If it's going to help users make a decision, I'll try and push for it now.
Click to expand...
Click to collapse
I'm shopping around for a new phone right now actually. First thing I always do when I find one that I seem interested in, is come here search and see can the bootloader be unlocked, what kernels are available, ROMs etc. Basically what kind of community support is behind the device. This is a large part of my decision to buy a phone. ROMs and kernels don't have be available right away, but if it's locked, support tends be lacking compared to other devices, so I tend to move along.
Again I'm sure I'm a minority, but if I want to change something, I want to be able to.
Unjustified Dev said:
The bootloader will be unlocked, I can push for it now, but I decided to wait to N. If it's going to help users make a decision, I'll try and push for it now.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I don't think ZTE has committed to N for the mini?
Hey!
I used to flash a lot of custom roms on my old phones (from X10 Mini Pro to HTC One M7).
Now I have a "new" (got it in December) S7 edge but fingers are itching as I really want to customize it.
I know that rooting and installing a Custom OS will void my warranty and trigger Knox but could I revert it all back?
In example when my Fingerprint Senser breaks but I run LineageOS, can I still revert to Stock with Knox back to normal etc, so the techs won't see that I rooted my phone?
Thanks in advance.
Now I could be wrong, but, I remember there being a way to rooting without tripping knox. Whether this is still possible, I'm not sure.
But, once it is tripped, it is gone. It is a physical fuse in the SoC which cannot be returned to normal Not good news
devblade said:
Now I could be wrong, but, I remember there being a way to rooting without tripping knox. Whether this is still possible, I'm not sure.
But, once it is tripped, it is gone. It is a physical fuse in the SoC which cannot be returned to normal Not good news
Click to expand...
Click to collapse
Thanks, I will probably wait until my warranty is gone then
Disapproved said:
Thanks, I will probably wait until my warranty is gone then
Click to expand...
Click to collapse
Maybe However, in some European countries you can quote directive 1999/44/CE which means that even with a software modification your provider must honour the warranty for hardware defects not caused by software. Therefore it might be worth doing.
Other functions such as S Health are not affected afaik as in custom roms this can be fixed by changing information in build.prop to get it working again.