eMMc issues/wrong read

[Predatorhaze]

Hello guys

some of us are facing some battery issues (sudden shutdowns,abnormal drain,abnormal charging etc) like me.
i never believed it was a hardware issue,and i still dont.

my axon 7G had b23 stock firmware + latest gpu drivers from raysteff.
i was thinking to try gsi again so i went to twrp and connect it with usb to make some backup transfers.My battery was 48%,after the backup i opend the display and battery shows 62%.
I flashed twrp treble from nfound,wiped everything and rebooted in edl and flashed nfound vendor partition trough miflash.Boot in twrp,Now my data was somehow encrypted and i decied to cancel the unlock and flash o b12 bootstack from nfound.Reboot to twrp again and data still encrypted,again i canceled the operation.I went to look at data partition and it shows the partition is emmc (yes finally again).I am thinkin a long time the battery issues are related to wrong emmc readings.(because the emmc never showd up anymore in that time i complained about battery % issues,even when i went to stock etc)

i continue flashing gsi+treble and will report how the battery act now.

booted my treble gsi system on 57%...when booted the system shows 49%....dropped to 47% in 1 minute and now its already like 10minutes on 47%. I know a first boot dont need 8% of the battery.Im 99% sure our phone are reading bad emmc stats but how can we find proof

 

[Predatorhaze]

MOD edit: Disrespectful towards developers! It always did before (before los15 etc)i even changed battery.
MOD edit: Disrespectful towards developers!

 

[EBeatFLA]

MOD edit: Disrespectful towards developers! It always did before (before los15 etc)i even changed battery.
MOD edit: Disrespectful towards developers!

Every, and i mean every, dev thread begins with a warning. No one is going to agree with you.

 

[SaintZ93]

??

So quick to blame others for your problems. How about thank us devs for what we brough to you guys. Without us you'd have nothing.

 

[Predatorhaze]

??

So quick to blame others for your problems. How about thank us devs for what we brough to you guys. Without us you'd have nothing.

not quick,this is alreadye here for months.MOD edit: Disrespectful towards developers!So many users complain about it.Its not my problem alone,and this problem is already here longer before my complains.
MOD edit: Disrespectful towards developers!....now you can say its ok,because you switched phone somehow after you swapped battery with a new one.

i also swapped battery and it didnt fixed the problem.

MOD edit: Disrespectful towards developers!

 

[pahoa]

not quick,this is alreadye here for months.MOD edit: Disrespectful towards developers!So many users complain about it.Its not my problem alone,and this problem is already here longer before my complains.
MOD edit: Disrespectful towards developers!....now you can say its ok,because you switched phone somehow after you swapped battery with a new one.

i also swapped battery and it didnt fixed the problem.

MOD edit: Disrespectful towards developers!

Seems like to me if you don't like these ROM's or appreciate what is freely given with no guarantees you should go back to stock. That is unless you really enjoy complaining, even though, no else cares to hear it.

 

[Masterjuggler]

MOD edit: Disrespectful towards developers!

I just read through your first post twice, and you are terribly confused. I don't understand if you are trying to work out battery issues or encryption issues, and I don't think you know what the term emmc means. What exactly are you trying to accomplish with this thread?

You've been given proper help and were taken seriously already, but you never gave any piece of advice a proper chance, and you certainly never received any help without immediately insulting the person helping you. If you think everyone you've grouped under the word "devs" are conspiring to only give you buggy software, maybe don't flash literally everything you come across without understanding how it works.

 

[Choose an username...]

not quick,this is alreadye here for months.MOD edit: Disrespectful towards developers!So many users complain about it.Its not my problem alone,and this problem is already here longer before my complains.
MOD edit: Disrespectful towards developers!....now you can say its ok,because you switched phone somehow after you swapped battery with a new one.

i also swapped battery and it didnt fixed the problem.

MOD edit: Disrespectful towards developers!

well, you said it. I'll tell you what you should do.

First of all, you should have checked whether the new battery was actually good before deciding it was fine. Since you're on a pretty bad situation already, I say you bite the bullet and buy a charge meter from Amazon or ebay. should cost less than $5, i'll leave a link down below for you to find one similar wherever you are. Just be sure that it displays mAh as there are some that only display V and mA. With this and offline charging you will have a much more precise way of knowing the state of your battery. This will be decisive and you'll be able to brag around that your problems are not caused by battery degradation ONCE YOU HAVE THE EVIDENCE. If that's the case, of course.
(Btw, you might still be in warranty, in that case you can send the battery back and they'll send you another. If your battery was stowed at very low voltage, it could have lost its capacity even before you got it).

That's on the hardware side of things. Even though i (and almost everybody else) don't believe that you have a software problem, if you want to be sure that it's not something that the BAD EVIL DEVS11!!1! did you can just brush up on which partitions are supposed to not be changed (like the persist), which partitions are flashed by an EDL package, and investigate on whichever lie in the middle (i.e. since you said an EDL flash didn't fix your supposed software problem, the two options are a. your battery is bad or b. the partition that has the bad, evil files is not rewritten by EDL).
Then ask for someone that's never went to custom ROMs for their whatever partition backup and flash it.




I don't think anybody is going to disagree with me that this is the most obvious way to clear this up. Also, if you simply ignore this and not do anything like you usually do, you'll lose even more credibility here even though you already have none. You asked for help, now use it and report back in a non-inflammatory way if possible.


btw, link to a battery meter
https://www.amazon.com/Minzhi-Curre...pacity+meter&qid=1551327256&s=gateway&sr=8-14

 

[AnonVendetta]

@Choose an username...: You are obviously clueless, by stating that persist is not supposed to be changed. You shouldn't format it, because it will remain empty and not repopulate, and caution should be taken when modifying its' contents. An empty persist will result in things like autorotate not working, sensors (GPS, etc), not working, perhaps an an inability to boot.

Unlike the system partition, persist is mounted as writable by default and isn't subject to dm-verity or system write restrictions, any file manager running with root authority can change its' contents. This applies not just to the A7, but by pretty much all phones that have a persist partition (nearly all). It is very much like data/cache except it is mainly used and written to by the Android OS behind the scenes, and isn't accessible to unrooted users.

I am of the opinion that @Predatorhaze's issues are mostly due to misinformation given to him by others, bad practices by him, and maybe a failing battery. The EMMC chip inside the device (it is a block storage device containing partitions, metadata, bootloader, etc) is mist likely fine. When it begins to fail that means your phone is on the way out and can only be fixed by installing a new motherboard. You will experiences symptoms like crashes, failure to boot, loss of data, seemingly random issues and other misbehavior.

Your logic is also sorely lacking, you can't lose what you dont have (addressing your reference to losing credibility when there is none).

You really don't know as much as you think you do. I wonder how many people have been tricked by your advice regarding battery calibration.

 

[Predatorhaze]

You call me clueless but wiping persist partition and then reboot,its all fine.files are back.I tried this because I have a persist backup to restore,but I didn't had to.

But thanks for answers

 

[Predatorhaze]

,you already told this.I even replaced battery. Voltages look weird too before and after.
It goes to warranty and never zte again

 

[AnonVendetta]

@Predatorhaze: Sure.....and I'm the one who provided you with that backup copy. Did @Choose an username... and others from Schwifty Telegram recommend you delete/format persist contents? Probably they did, but as a joke. I don't call that helping someone. When I was there they did mention that they told you to do a "deep wipe" (low level format of the EMMC chip and all its' partitions and their contents). And they said that you did so.

They clown you behind your back like you're nothing, if I were you I'd stop listening to them or taking any advice they offer. Admittedly, you brought some of it on yourself, though.

If I post in any thread then I'm just trying to help, I don't get kicks by trying to help someone do something that will wreck their phones. You can take my posts as constructive criticism.

 

[SaintZ93]

@Predatorhaze: Sure.....and I'm the one who provided you with that backup copy. Did @Choose an username... and others from Schwifty Telegram recommend you delete/format persist contents? Probably they did, but as a joke. I don't call that helping someone. When I was there they did mention that they told you to do a "deep wipe" (low level format of the EMMC chip and all its' partitions and their contents). And they said that you did so.

They clown you behind your back like you're nothing, if I were you I'd stop listening to them or taking any advice they offer. Admittedly, you brought some of it on yourself, though.

If I post in any thread then I'm just trying to help, I don't get kicks by trying to help someone do something that will wreck their phones. You can take my posts as constructive criticism.

Nope not once did anyone recommend him to wipe his persist and no one would ever recommend a deep wipe. Know your facts before pointing fingers. You are just as low as him. He came into the group asking for help, we gave him all the advice then he started bashing. He went ahead and did his own thing came back and said he did a "deep wipe" which is probably why he has all these issues now. We stopped supplying him help because he just runs his mouth just like you. Im glad I moved on from this phone. People like you and him ruin the dev community for phones.

 

[AnonVendetta]

@SaintZ93: Yeah sure I ruin dev communities...by donating money to devs that deserve it, providing constructive criticism and feedback in their threads, encouraging them to keep up the good work instead of constantly complaining, posting issues/bug reports on GitHub etc. I totally respect your work as a dev, Schwifty is solid. But with that said, I do remember with 110% certainty that @Choose an username... said that you guys jokingly recommended he do a deep wipe, he took it seriously. Too bad I didn't keep screenshots of the chat, then there would be proof.

 

[Choose an username...]

@Choose an username...: You are obviously clueless, by stating that persist is not supposed to be changed. You shouldn't format it, because it will remain empty and not repopulate, and caution should be taken when modifying its' contents. An empty persist will result in things like autorotate not working, sensors (GPS, etc), not working, perhaps an an inability to boot.

Unlike the system partition, persist is mounted as writable by default and isn't subject to dm-verity or system write restrictions, any file manager running with root authority can change its' contents. This applies not just to the A7, but by pretty much all phones that have a persist partition (nearly all). It is very much like data/cache except it is mainly used and written to by the Android OS behind the scenes, and isn't accessible to unrooted users.

I am of the opinion that @Predatorhaze's issues are mostly due to misinformation given to him by others, bad practices by him, and maybe a failing battery. The EMMC chip inside the device (it is a block storage device containing partitions, metadata, bootloader, etc) is mist likely fine. When it begins to fail that means your phone is on the way out and can only be fixed by installing a new motherboard. You will experiences symptoms like crashes, failure to boot, loss of data, seemingly random issues and other misbehavior.

Your logic is also sorely lacking, you can't lose what you dont have (addressing your reference to losing credibility when there is none).

You really don't know as much as you think you do. I wonder how many people have been tricked by your advice regarding battery calibration.

Lol. you're just grasping at how little there is...
Persist shouldn't be changed after the phone comes out of the factory, because it contains some sensor calibration files. i'm not saying it doesn't ever get written, and i literally said below that line that he could even try getting a brand new persist backup from another phone because that's probably the best he can do (assuming he hasn't got one from his own phone)

Your logic is also sorely lacking, you can't lose what you dont have (addressing your reference to losing credibility when there is none).

and about this? Don't even try.

I've seen the PMs that you sent to other people here, and i'm not gonna bite to your BS bait

---------- Post added at 01:35 PM ---------- Previous post was at 01:33 PM ----------

@SaintZ93: Yeah sure I ruin dev communities...by donating money to devs that deserve it, providing constructive criticism and feedback in their threads, encouraging them to keep up the good work instead of constantly complaining, posting issues/bug reports on GitHub etc. I totally respect your work as a dev, Schwifty is solid. But with that said, I do remember with 110% certainty that @Choose an username... said that you guys jokingly recommended he do a deep wipe, he took it seriously. Too bad I didn't keep screenshots of the chat, then there would be proof.

Mike's right, it's an inside joke because he deep wiped the phone and said it made his phone detect two batteries. guess you remember wrong

---------- Post added at 01:53 PM ---------- Previous post was at 01:35 PM ----------

,you already told this.I even replaced battery. Voltages look weird too before and after.
It goes to warranty and never zte again

so, you ignored me completely. Your battery being new doesn't mean that it didn't arrive trashed to your door.

Good, though. Swap the axon for something else, and call it a day

 

[Choose an username...]

@AnonVendetta here are your screenshots. have fun
Straight from source

 

[SaintZ93]

@AnonVendetta here are your screenshots. have fun
Straight from source

This is why people need to know their facts like I said before pointing fingers and blaming us for stuff we didn't say or do, preferably you Anon. Hope you stand corrected now.

 

[AnonVendetta]

@Choose an username...: You win there. But your logic is still screwed, because I wasnt even present during that convo. Those screens are from way before I ever showed up. When I said I recall, that logically means I would have had to be there, regardless of whether the memory is incorrect or not. And since you admit that it was an inside joke, that basically means you were trying to help him screw over his phone.

I really couldnt help busting out laughing after looking at the pics, @Predatorhaze dug his own grave. I mean, he mentioned deep wipe so many times, it's as if something was compelling him to do it. Clearly his own idea.
@Predatorhaze: Do yourself a favor, go smash your phone repeatedly with a hammer, at least then you can save yourself from listening to the advice of members that don't care to help anyway. There are newer phones out there, move on.

 

[Choose an username...]

@Choose an username...: You win there. But your logic is still screwed, because I wasnt even present during that convo. Those screens are from way before I ever showed up. When I said I recall, that logically means I would have had to be there, regardless of whether the memory is incorrect or not. And since you admit that it was an inside joke, that basically means you were trying to help him screw over his phone.

I really couldnt help busting out laughing after looking at the pics, @Predatorhaze dug his own grave. I mean, he mentioned deep wipe so many times, it's as if something was compelling him to do it. Clearly his own idea.

@Predatorhaze: Do yourself a favor, go smash your phone repeatedly with a hammer, at least then you can save yourself from listening to the advice of members that don't care to help anyway. There are newer phones out there, move on.

may I ask, what logic is screwed now? You said I told Ter that, then a) we told you you were wrong, nothing more than that, and b) i sent screenshots proving that Ter was the one to jump on the deep wipe train. i never told you you should have known, which is what i assume you are peddling around here

 

[AnonVendetta]

@Choose an username...Are you *THAT* dumb? Since I wasn't there at the point during your screens, then I couldnt possibly know what was said then. I was recalling from the time I was there (and he wasn't), what was said. So if you want to also dig up screens of that too...