Hi Community. Kind of a noob here, but I'll try to be as specific as possible.
So let me start. I was using custom roms on my Mi A1 a few days back, and decided to change back to stock. So I went ahead and downloaded the April Fastboot room for Tissot from their official MIUI website.
Flashed the room through Mi A1. Selected Clean all and lock from the bottom menu of Mi Flash. The process went without any hiccups.
As soon as I booted up the phone, found out Wi-Fi wasn't working. Came to know that custom rooms tend to change the default MAC address of the phone. Didn't know that at the moment, but unfortunately kept flashing different versions, and lost the Persist Partition.
This is where I screwed up really bad. I selected Clean factory(something like that). Lost my IMEI. Saw a guide on XDA about flashing someone else's Persist Image and screwed up big time. All sensor calibration data was lost. Restored IMEI through QPST. But the sensors aren't getting detected by the phone. To be specific, Accelerometer, Gyroscope and Compass. This is all the information I have on which sensors aren't working anymore. What should I do?
I went to Mi authorised service center, waited for like 4 hours and what they told me was
1.This was done by Liquid Damage
2. You're out of Warranty(Due to 1)
3. We need to change both the main board and the sub-board
4. The estimation sweeps in around RS.6100(94$).
Considering the actual price of a brand new Mi A1, that comes in around 215$, that would be too much for me to put out.
Can anyone provide me with a solution? Thanks for looking at this post.
sandhikshyan said:
Hi Community. Kind of a noob here, but I'll try to be as specific as possible.
So let me start. I was using custom roms on my Mi A1 a few days back, and decided to change back to stock. So I went ahead and downloaded the April Fastboot room for Tissot from their official MIUI website.
Flashed the room through Mi A1. Selected Clean all and lock from the bottom menu of Mi Flash. The process went without any hiccups.
As soon as I booted up the phone, found out Wi-Fi wasn't working. Came to know that custom rooms tend to change the default MAC address of the phone. Didn't know that at the moment, but unfortunately kept flashing different versions, and lost the Persist Partition.
This is where I screwed up really bad. I selected Clean factory(something like that). Lost my IMEI. Saw a guide on XDA about flashing someone else's Persist Image and screwed up big time. All sensor calibration data was lost. Restored IMEI through QPST. But the sensors aren't getting detected by the phone. To be specific, Accelerometer, Gyroscope and Compass. This is all the information I have on which sensors aren't working anymore. What should I do?
I went to Mi authorised service center, waited for like 4 hours and what they told me was
1.This was done by Liquid Damage
2. You're out of Warranty(Due to 1)
3. We need to change both the main board and the sub-board
4. The estimation sweeps in around RS.6100(94$).
Considering the actual price of a brand new Mi A1, that comes in around 215$, that would be too much for me to put out.
Can anyone provide me with a solution? Thanks for looking at this post.
Click to expand...
Click to collapse
My sensors stopped working too. Now I have a broken screen AND dead sensors ?
JaadiBooti said:
My sensors stopped working too. Now I have a broken screen AND dead sensors ?
Click to expand...
Click to collapse
Seriously. Will no one help? I can't shell out 7500 for this phone.
sandhikshyan said:
Seriously. Will no one help? I can't shell out 7500 for this phone.
Click to expand...
Click to collapse
Head over to guides section.. multiple tutorials are thr about presist restore
Try to flash a fastboot Nougat stock Rom with complete wipe. You have nothing to loose.
http://bigota.d.miui.com/7.11.18/tissot_images_7.11.18_20171117.0000.00_7.1_3ac9b1f856.tgz
sandhikshyan said:
Seriously. Will no one help? I can't shell out 7500 for this phone.
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-fix-broken-sensors-stock-t3789900
I had persist partition problems, I flashed in edl mode, changing the rawprogram0 to add in persist.img, but now I have no sensors.
Also for me 'On-body detection' didn't show up in the Smart Lock, and I followed the YouTube video below and everything is working!
Well 99.9% working, the Bluetooth shows up on macvendors.net as 'No Vendor', so hopefully you have the .bt_nv.bin backed up, because for me /persist/bluetooth was empty. I had the original .bt_nv.bin, so I added it in, now I am using Xiaomi Vendor Mac...
https://www.youtube.com/watch?v=Qf0XhhnpQEo
Also if WiFi not working, then check this post, reply from SevenSlevin;
https://forum.xda-developers.com/showpost.php?p=76829117&postcount=118
Thanks
Related
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Seriously???
pastorbob62 said:
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Click to expand...
Click to collapse
Not to be negative or anything but I think this is the least responsive forum on this site. I have spent hours searching for possible solutions to various problems I've encountered over the past several months, asked several questions and received little if any help. I was only able to get back from a bricked phone to where I am now by using information found on other websites. Pretty sad if you ask me.
In contrast, whenever I have asked a question on my tablet's forum I've received fast workable solutions/answers to my problems/queries. The threads are informative, well organized and contain answers to any situation I have encountered.
Granted, my current problem with my phone is my own fault for trying to customize it. And I suspect part of the problem is due to the age of this phone thus most of the "experts" have moved on to other ventures. It is also hindered by the lack of information available from Huawei and the service providers.
All of that said, if anybody has any suggestions for how I can repair the ESF partition or whatever is causing this lack of mobile service issue I would be extremely grateful. It isn't the end of the world since i have a new phone (Consumer Cellular) that I am currently using but it would be great to get this one working since it's much faster and more streamlined than my stock Consumer Cellular version.
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
Thank you very much for your reply. It seems that you have found the answer to my problem. But unfortunately, I don't have a copy of the original stock ROM. My phone is the -51 version and any links I have found to the stock ROM are broken. There is a version I found but it is for Venezuela and I don't think it will work. I am leery to try it and totally brick my phone. My backup is apparently corrupted. I backed up my new working phone with Disk Image and attempted to restore it to the broken phone but all that did was cause it to come up to the ATT logo screen for a few seconds and then shut down. It wouldn't do anymore than that. So I restored the Stallion 3.5 image I made and am back to a great fast tablet with no phone service. I also tried backing up my IMEI on the working phone and restoring it to the broken phone but that had no effect.
It is my understanding that the -Pro version of the ROM will work, but I don't have the stock image of that either. I suspect it work might since I was able to use the -Pro version of GB on it. All of my internet searches have only turned up custom ROMs and other desperate people looking for fixes for similar problems or worse. I agree 100% with your assessment of Huawei's lack of meaningful support. It really is a shame, because these phones aren't half bad when they have been customized and OC'ed a little.
I have just about given up on it and resigned myself to using it as an MP3 player for my car system. I have learned my lesson and am leaving the working phone stock. It is rooted and I have cleaned off all of the bloatware, and set it up so most apps run from my SD card, so it really isn't half bad. At least it works.
Again, thank you for your reply and advice.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
ggunzio said:
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
Click to expand...
Click to collapse
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Blefish said:
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Click to expand...
Click to collapse
i have exactly the same phone than you, because i installed that backup too. After installed it, the IMEI SV is 36, after installing B518 it says it is 18, but before it was 17, and i had 3g signal, but not now.
My question is, wich SV is your phone reporting?
Thank you
I also have a problem like this, but I think it's a bit more severe. My phone got stuck while charging. Couldn't reboot. Was getting stuck on the aurora loading screen(using DZO 5u20). Than reinstalled whole rom. But now I don't any signal and the phone doesn't even see a SIM card. Showing 'baseband unknown' and the IMEI and IMEI SV are also unknown. Not 0's but just unknown. Is this is a similar problem? And can something be done to fix it.
I had some backups on my sd card, untill the sd-card got fried in the phone a couple of months ago.
Yah, I'm serious! I'll tell you in detail.
Weeks ago, when I tried to flash stock rom, I made a big mistake that made my deivice hard bricked and then I found the reason in this thread: https://in.c.mi.com/thread-1095941-1-0.html.
I immediately brought my device to Mi Support Center, they made it alive but other problems came and I posted this thread: https://forum.xda-developers.com/mi-a1/help/help-soft-brick-t3860620 (thanks for people who tried to help me)
I found that my device lost persist partition, so that I flashed it, done, however, I relized that my device lost IMEI and BASEBAND, too.
I tried to restored my IMEI by QCN file but I only got sim 1 IMEI, I flashed BASEBAND and my deivice stuck in bootloop.
After a long time, I asked for someone to help but they couldn't do anything and then I found some problems.
1. IMEI dosen't show anything now and BASEBAND is unknown.
2. I can't flash Android 8.1 or higher versions on my device, it only accepts 8.0 and lower versions. If I flash 8.1, it continuously reboot when Android One logo shows up. But nothing happens when I flash 8.0.
Three days ago, I brought my device to Mi Support Center again, they said my mainboard is broken, it need replacing but I denied because the cost is too expensive, about $145. I took it back, tried to flash 8.0 version and installed update, sadly, my device is locked now and I can't flash anything. I think I can flash 8.0 via testpoint method, but the important thing is that I don't know what's exactly happenning with my device.
Why I can't flash 8.1 version and can I take my IMEI back?
I'm tired to find the answers days and I'm thinking to sell my death device with a cheap price about $40 for screen and camera only.
Someone help me, please!
By the way, I'm in Vietnam.
manhnl311 said:
Yah, I'm serious! I'll tell you in detail.
Weeks ago, when I tried to flash stock rom, I made a big mistake that made my deivice hard bricked and then I found the reason in this thread: https://in.c.mi.com/thread-1095941-1-0.html.
I immediately brought my device to Mi Support Center, they made it alive but other problems came and I posted this thread: https://forum.xda-developers.com/mi-a1/help/help-soft-brick-t3860620 (thanks for people who tried to help me)
I found that my device lost persist partition, so that I flashed it, done, however, I relized that my device lost IMEI and BASEBAND, too.
I tried to restored my IMEI by QCN file but I only got sim 1 IMEI, I flashed BASEBAND and my deivice stuck in bootloop.
After a long time, I asked for someone to help but they couldn't do anything and then I found some problems.
1. IMEI dosen't show anything now and BASEBAND is unknown.
2. I can't flash Android 8.1 or higher versions on my device, it only accepts 8.0 and lower versions. If I flash 8.1, it continuously reboot when Android One logo shows up. But nothing happens when I flash 8.0.
Three days ago, I brought my device to Mi Support Center again, they said my mainboard is broken, it need replacing but I denied because the cost is too expensive, about $145. I took it back, tried to flash 8.0 version and installed update, sadly, my device is locked now and I can't flash anything. I think I can flash 8.0 via testpoint method, but the important thing is that I don't know what's exactly happenning with my device.
Why I can't flash 8.1 version and can I take my IMEI back?
I'm tired to find the answers days and I'm thinking to sell my death device with a cheap price about $40 for screen and camera only.
Someone help me, please!
Anyway, I'm in Vietnam.
Click to expand...
Click to collapse
Do a data format, then install anything.
justboryata said:
Do a data format, then install anything.
Click to expand...
Click to collapse
How to flash something when bootloader is locked? Anyway, that's not point, I can flash via testpoint method, the point is why I can't use 8.1 and can I take my IMEI back, thanks!
manhnl311 said:
Yah, I'm serious! I'll tell you in detail.
Weeks ago, when I tried to flash stock rom, I made a big mistake that made my deivice hard bricked and then I found the reason in this thread: https://in.c.mi.com/thread-1095941-1-0.html.
I immediately brought my device to Mi Support Center, they made it alive but other problems came and I posted this thread: https://forum.xda-developers.com/mi-a1/help/help-soft-brick-t3860620 (thanks for people who tried to help me)
I found that my device lost persist partition, so that I flashed it, done, however, I relized that my device lost IMEI and BASEBAND, too.
I tried to restored my IMEI by QCN file but I only got sim 1 IMEI, I flashed BASEBAND and my deivice stuck in bootloop.
After a long time, I asked for someone to help but they couldn't do anything and then I found some problems.
1. IMEI dosen't show anything now and BASEBAND is unknown.
2. I can't flash Android 8.1 or higher versions on my device, it only accepts 8.0 and lower versions. If I flash 8.1, it continuously reboot when Android One logo shows up. But nothing happens when I flash 8.0.
Three days ago, I brought my device to Mi Support Center again, they said my mainboard is broken, it need replacing but I denied because the cost is too expensive, about $145. I took it back, tried to flash 8.0 version and installed update, sadly, my device is locked now and I can't flash anything. I think I can flash 8.0 via testpoint method, but the important thing is that I don't know what's exactly happenning with my device.
Why I can't flash 8.1 version and can I take my IMEI back?
I'm tired to find the answers days and I'm thinking to sell my death device with a cheap price about $40 for screen and camera only.
Someone help me, please!
By the way, I'm in Vietnam.
Click to expand...
Click to collapse
These files were dangerous dude and they brick parts of your motherboard like imei and baseband. So if you need a fix replace it
billis2020 said:
These files were dangerous dude and they brick parts of your motherboard like imei and baseband. So if you need a fix replace it
Click to expand...
Click to collapse
I can buy a new one with the cost to replace to the whole mainboard. In fact, I accept the thing that I can't use SIM anymore, I just don't know why I can't upgrade to 8.1 or higher
Hey all......I created a thread awhile back when I borked my phone trying out a new treble rom that was supposed to be so easy even a nOOb could flash it, and it ended up messing up my phone to the point where the only way for me to get it back was to follow the thread to disassemble the phone and short the chip out.
Then, the screen was not responsive on ANY rom I flash except for MM and it worked with any up to B29. I tried a few times to upgrade all in vain but I was always able to flash MM B29 and have it work again.
Flash forward to last night and my itchy trigger upgrade finger did it again and I attempted to flash the Oreo from ZTE. It flashed fine but, again, no responsive screen. I thought well, maybe I could try Nougat again and I flash many different versions and in different ways (used miFlash, EDL tool, MiFavor recovery, twrp) and all resulted in the screen not being responsive. Sigh, so I flashed MM B29 but now it will not detect any sim or even allow wifi to be turned on.
I have tried multiple times to reflash MM B29 using all the different ways above and even went back and forth between roms. I tried the original way most of us first unlocked the bootloader and flashed through all those stepped zip packages from B20 to B29 and still nothing. I finally used twrp to erase/format all data and made certain the partitions were formatted as ext4 and tried again, still no sim.
I realize that my imei is not showing and even tried a program to flash? that to the phone.
NOW, what needs to be said is during ALL of this flashing the phone signal/sim DID show......yes.......the sim DID WORK......when I flashed anything other than MM B29. LOL. Of course, the issue is none of those roms allow the screen to work.
Please, if anyone can help I would appreciate it very much. I'm thinking by flashing the Oreo from ZTE it may have changed something that the MM B29 rom is not changing to allow the phone to read the imei/sims.
I'm not sure but I think the DFU multitool posted by @raystef66 can fix the IMEI issue.
You have installed the correct modem for you device? EG: if you've flashed a U modem on a G device the sim and WiFi won't work.
If this is correct check APN and network setting in the phones software.
I hope this helps ?
Syberclone said:
I'm not sure but I think the DFU multitool posted by @raystef66 can fix the IMEI issue.
You have installed the correct modem for you device? EG: if you've flashed a U modem on a G device the sim and WiFi won't work.
If this is correct check APN and network setting in the phones software.
I hope this helps
Click to expand...
Click to collapse
I appreciate the suggestions. Unfortunately, the DFU tool doesn't seem to work for me as it remains listed as Disconnected even after choosing the correct port.
I have always flashed the MM B29 EDL rom (A2017U_B29_MARSHMALLOW_FULL_EDL) that contains the correct modem. As I said, it always worked before.
As far as checking APN/network settings, well, there are none to check because the sim is not detected so all of those choices are greyed out. The signal bars fr both sims are blank in the notification area and of course wifi does not turn on.
I just finished another round of trying different roms to flash including LOS 15. LOS came up to the welcome screen (just like all the others) AND the AT&T logo with LTE full signal bars showing. Again, the screen does not respond to touch so it's all useless. I am at a loss as to why flashing MM B29 is no longer working for me.
Stop using guides mentioned in Axon7 thread,or stop listening to other users.Only thing i see here are bricks.
Probably you have hardware fault
The Axon 7 has been the worst phone for being bricked.
I've flashed ROMs on HTC's, Motorola and Google phones all without problems.
There are way too many packages and bootstacks etc, etc that cause problems and confusion.
So I wouldn't say don't follow threads or users advice.
My advice is research, research and research some more.
Thanks for the suggestions.
Something to get clear.....
I can successfully flash the roms and get to the Welcome screen to begin setup.
MARSHMALLOW:
-screen does respond to touch
-sims are NOT detected
-no AT&T logo
-no phone signal
ANY OTHER VERSION (Nougat, Oreo):
-screen does NOT respond to touch
-sims are recognized
-AT&T logo appears
-phone signal strength meter shows full bars
So, it's not a hardware fault. The phone was working perfectly fine when I had Marshmallow flashed. It's only this last time I flashed the Oreo from ZTE's website and when that did not work I tried a few other roms and then went back to the Marshmallow B29 EDL that I had been using all along.
Isn't there a way to COMPLETELY wipe this phone and start from scratch? As in, when your Windows is so full of crap and running slow you can format the hard drive and reinstall Windows from scratch. I have tried TWRP and format data (have to type yes to format) etc........is there a way to format w=everything that might affect the sim from being detected in Marshmallow? Better yet, the screen from being responsive in other ROMS after marshmallow?
djprez said:
Thanks for the suggestions.
Something to get clear.....
I can successfully flash the roms and get to the Welcome screen to begin setup.
MARSHMALLOW:
-screen does respond to touch
-sims are NOT detected
-no AT&T logo
-no phone signal
ANY OTHER VERSION (Nougat, Oreo):
-screen does NOT respond to touch
-sims are recognized
-AT&T logo appears
-phone signal strength meter shows full bars
So, it's not a hardware fault. The phone was working perfectly fine when I had Marshmallow flashed. It's only this last time I flashed the Oreo from ZTE's website and when that did not work I tried a few other roms and then went back to the Marshmallow B29 EDL that I had been using all along.
Isn't there a way to COMPLETELY wipe this phone and start from scratch? As in, when your Windows is so full of crap and running slow you can format the hard drive and reinstall Windows from scratch. I have tried TWRP and format data (have to type yes to format) etc........is there a way to format w=everything that might affect the sim from being detected in Marshmallow? Better yet, the screen from being responsive in other ROMS after marshmallow?
Click to expand...
Click to collapse
Did you installed a vendor partition?
Predatorhaze said:
Did you installed a vendor partition?
Click to expand...
Click to collapse
I am not certain. If the Oreo update that I downloaded directly off the ZTE site has one, then yes. If that is the cause, how would I modify it?
@djprez: To my knowledge, ZTE's official B12/B20 do not have a vendor partition. ZTE will almost certainly never add Treble support for the A7, if they are going to do so then now is an ideal time, since the A7 is an end-of-life device and no longer being manufactured.
Hello guys
Firtst of all: sorry for my english. Second: I can't post in the dev section because of my low post count, so here I am.
I think this is a very particular thing and maybe a developer's answer is required. The main problem is: my Redmi Note 7 (a phone that I love) has a big problem that is spreaded in more than one Xiaomi phone, I'm talking about the bug on the proximity sensor. In few words, when I'm on a call (no matter if I received it or I am the caller) the screen turns on and I accidentally press e.g. the data connection button, turning them off. Same thing with vocal notes on Whatsapp and Telegram. I noticed that this problem occurs especially when I'm under direct light, by night is less frequent.
Looking around in some forums, the majority of users told me that it's software bug that can I solve with some workarounds, while waiting for an official fix. They told me to reboot my device, they told me to recalibrate the sensor using the secret test menu, they told me almost anything and I've tried everything to solve this pain in the *** but nothing seems to solve it. Anyway, a user told me that by installing magisk I can fix it, but I can't see any correlation between root permission and proximity sensor, am I missing something?
Beside root permission, I've come out with a new information that I didn't know: in Android there is a specific partition in which is stored all the settings and parameters used by all the sensors, the persist partition (or persist.img) and I was thinking if it's possibile to "edit" those data, I read about a difficult procedure to get stock settings from compressed MIUI rom to put them in place of the actual one inside the phone, this procedure involves ADB and TWRP if I remember well. Can someone give me more informations/advice/whatever about this thing?
I really want to get rid of this problem, sometimes the phone is useless...
Hi! i don't know how is the ZIP file for redmi note 7, but, in previous xiaomi phones i bought, the ZIP file from the official xiaomi page had the persist.img file in it, with unlocked bootloader, adb drivers installed on your PC, the phone on fastboot and connected, you only write on CMD: fastboot flash persist persist.img
Hi.
First of all, I want to let you know I'm just new to this page, so I'm so sorry if I make any mistakes within creating the post.
As you've read in the title, I can't fix the OS of this phone. I bought it used, and apparently it didn't have any OS (I thought it was because there was a flashing attempt, which went wrong). One day, I just looked for Android 9 and I installed it. The phone started working, and so I started using it. There were some problems with the phone though. First of all, at random moments, it started lagging and just re-starting. The other problem I had was the bootloader message, saying that I didn't have an official OS.
Today, I tried to uninstall all of /system. I read a lot of information, I watched a lot of videos and I started doing so. Basically, what I wanted to do is delete all in /system so I could install a clean ROM from my computer. Problem is, I have "flashing_locked" flag. I also downgraded it to Android 8, and I think it made it worse. Now, I don't even have internet connection (or what is called /persist), which also means I'm stuck in the setup screen. There's no way I have now to enter developer mode, nor activating usb debugging. Just wondering, is there any tips I could get from you guys to fix all this problem?
Thanks a lot.
Edit: I also think there's some "residual" data from those flashing attempts, Android 8 and also Android 9. I'm not sure if that has something to do.
Edit 2: I also requested a Unique Key from the Motorola official page, which didn't lead me to anywhere. Although I used "fastboot oem unlock <key>", it didn't work to me.
s9kii_ said:
Problem is, I have "flashing_locked" flag.
Click to expand...
Click to collapse
I'm wondering how you managed to downgrade the device from Android 9 to 8 with a locked bootloader?? that's very strange... To fix the known issue of broken wifi/mobile connection (as a result of the downgrade) it's recommended to revert back to Android 9.
So, you did the downgrade from 9 to 8. But now you can't finish the setup wizard to activate OEM unlocking? Please tell me, at which point it has been deactivated?? It doesn't make any sense...
Try the Lenovo Motorola Smart Assistant tool. It'll fix the issue.
s9kii_ said:
I also think there's some "residual" data
Click to expand...
Click to collapse
I think not. Flashing a firmware means copying image files to a specific partition. Each image file got its own partition table. There will be no data left.