greetings,
i try to make it short:
10month ago i bought 3x LG V20 H918 t-mobile brand from ebay, came from HK, same seller
same modell all same same only imei different, me living in germany.
1/3 i bootloader unlocked, rooted with magix, twrp and back to version 20H
up and running fine as EDC , no issues, until yesterday, when it died finally after fuqqed up screen.
so i took 2/3, same process, bootloader unlock, root magisk twrp etc. following the guide i used
to write as simple as possible back in the day. i restored the backup i made with phone 1/3, thing up and running in about 1h.
but it shows simlock ! i have some possibilitys left, ill try lineage OS etc maybe different kernel,
but since im by far no pro with android, my possibilities are limited. did i do s.t. wrong?
i tried different versions of twrp, since it showed the "can not decrypt" screen many times, i tried different versions of stock rom,
i tried using the backup from phone 1/3 and clear install of stock rom, wiped data/system/everything (except micor sd)
always simlock.
any ideas are much appreciated, why does phone 2/3 has simlock, while phone 1/3 was up without any issues :/
thx
for now, i exchanged the mainboards (mainboard from phone 1/3 --> phone 2/3) up and running.
from phone 1/3 only screen was destroyed, mainboard was still fine)
not the smoothest solution but ok for now.
i contacted t-mobile US they seemed to be a little overwhelmed by my concern.
it seems with normal methods there is no chance of getting rid of that simlock, since its supposed to be on a hidden partition on internal memory, and there is just no way to access this one, except with the unlocking code.
when trying to check IMEI from phone 2/3 and enter *#61# (?) it showed IMEI 0....
if s.o. has any ideas on how to extinguish scumsimlock, still much appreciated.
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.
Hi there,
I realy need your help on my problems with the G2 32GB D802.
I bought it on ebay and instead of getting it from GB it came from HongKong and I didn't think about it that it does not have a european ROM.
First I wanted to root and flash custom recovery and cloudyG3 rom. After rooting with ioroot and installing the TWRP I stuck in the fastboot mode. First problem I did not make a backup because I never reached TWRP. Download mode only appeared for a second an then disappeared again.
After a lot of searching I found that probably the 802autorec.apk was wrong, since I don't have a european model. So I installed via fastboot a laf.img for a D800. After that the download mode was working again and I installed different roms via flashtool2014. The installation worked again but after rebooting the phone I had a lot of trouble with it. That the reason for trying different roms as I sad befor.
First, the fingertip points at different areas of the screen but not there where you are touching the screen. So you can not reach the buttons or write on the keyboard.
Second, after connection to pc I recognized that my 32GB model had only 10GB internal memory.
Finaly I can not use the phone. For me it seems that I burned my partitions and need your help to get it right again.
Please give me a chance.
Best regards an thanks for helping me.
p.s.: I tried to go to the settings menu in the phone and reached it after a lot of confusing taps on the screen. All the phones informations like IMEI and all the other disappeared. Something realy went wrong with it.
No one an idea how to get back to normal?
frankhell said:
No one an idea how to get back to normal?
Click to expand...
Click to collapse
I have the same problem. Bought LG G2 D802, wifi connection was weak. I downloaded Lg PC Suite and upgraded the system. After upgrade have the same touchscreen problem. Have tested for 5-6 firmwares, but the problem is.
Do not exactly know what firmware need to install.
Please help us.
enter enginnering mode and update the touch firmware may work for you？
frankhell said:
Hi there,
I realy need your help on my problems with the G2 32GB D802.
I bought it on ebay and instead of getting it from GB it came from HongKong and I didn't think about it that it does not have a european ROM.
First I wanted to root and flash custom recovery and cloudyG3 rom. After rooting with ioroot and installing the TWRP I stuck in the fastboot mode. First problem I did not make a backup because I never reached TWRP. Download mode only appeared for a second an then disappeared again.
After a lot of searching I found that probably the 802autorec.apk was wrong, since I don't have a european model. So I installed via fastboot a laf.img for a D800. After that the download mode was working again and I installed different roms via flashtool2014. The installation worked again but after rebooting the phone I had a lot of trouble with it. That the reason for trying different roms as I sad befor.
First, the fingertip points at different areas of the screen but not there where you are touching the screen. So you can not reach the buttons or write on the keyboard.
Second, after connection to pc I recognized that my 32GB model had only 10GB internal memory.
Finaly I can not use the phone. For me it seems that I burned my partitions and need your help to get it right again.
Please give me a chance.
Best regards an thanks for helping me.
p.s.: I tried to go to the settings menu in the phone and reached it after a lot of confusing taps on the screen. All the phones informations like IMEI and all the other disappeared. Something realy went wrong with it.
Click to expand...
Click to collapse
I now have the answer from the dealer that my G2 has the Firmware D80220B.
Just try and test it. Good luck.
@Angryyolk
I just ask myself how to enter engeniering mode?
Thanks for your help.
I walked one step forward now.
But there is still no solution for my problem. I found a link to LG "http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=IMEI" to get the information about the version of my stock ROM. Just replace IMEI by your real number and you will get it.
In the meantime I flashed the rom with flashtool but the screen behaviour is still the same.
I later rooted the phone with towleroot and then installed the correct autorek.apk for the D802. That worked properly. I reached TWRP but in fact of the weired screen behaviour I couldnt do something. I tried to fix my IMEI problem with QPST but this tool showed only empty tables on my PC when I connected my G2 with usb.
I tried an update of the screen firmware as posted above. The code that has to be entered on the dialer is 3845#*802# but it wont work for me since I can't enter "settings" the service menu. That's because of the weired behaviour.
Beste regards
I now was able to enter the hidden menu. And I was able to get to the menu point "update touch firmware" but nothing happend.
What is wrong?
touch screen problem
The same problem occurred on my phone. how did you do it. please help.
I installed the software and touch screen freaked out.
It's because its a Refurbished Models..
You have to check your Mother board for exact Model
Sent from My LG G Flex LG-F340K Stock KitKat V20D on LTE Network using XDA Free Mobile app
Hello,
Yesterday I got a brand new D802, I can't tell you what kernel it is or baseband because my device isn't working properly.
the problems began after I did an upgrade from D80210B to D80210D using the LG PC Suite.
after the upgrade was done, the touch screen got very erratic and I every place I've touched wasn't the right place (it acted like it wasn't calibrated)
I've tried to flash the stock ROM again using LG Flash Tool 2014 and using both Hong Kong 32GB D80210D_00.kdz and Hong Kong 32GB D80210B_00.kdz files but it didn't do any good.
I can't enter recovery mode, I get only the Factory reset screen (which I did twice and no good either).
one more thing I've noticed is that the device doesn't recognize any SIM card I out in it, at first it recognized my SIM (I have a giffgaff SIM) and after the upgrade the boot screen suddenly showed me the Vodafone logo.
I ever tried to put a Vodafone SIM in it, but the results were the same. If I'm not doing anything, the device boot itself into a loop, I can see the first screen of the initialization but that's it.
I've managed to get it to work one time but I couldn't even operate it on a basic level and the touch was erratic.
many thanks for any help that I would get.
Ice_machinE said:
Hello,
Yesterday I got a brand new D802, I can't tell you what kernel it is or baseband because my device isn't working properly.
the problems began after I did an upgrade from D80210B to D80210D using the LG PC Suite.
after the upgrade was done, the touch screen got very erratic and I every place I've touched wasn't the right place (it acted like it wasn't calibrated)
I've tried to flash the stock ROM again using LG Flash Tool 2014 and using both Hong Kong 32GB D80210D_00.kdz and Hong Kong 32GB D80210B_00.kdz files but it didn't do any good.
I can't enter recovery mode, I get only the Factory reset screen (which I did twice and no good either).
one more thing I've noticed is that the device doesn't recognize any SIM card I out in it, at first it recognized my SIM (I have a giffgaff SIM) and after the upgrade the boot screen suddenly showed me the Vodafone logo.
I ever tried to put a Vodafone SIM in it, but the results were the same. If I'm not doing anything, the device boot itself into a loop, I can see the first screen of the initialization but that's it.
I've managed to get it to work one time but I couldn't even operate it on a basic level and the touch was erratic.
many thanks for any help that I would get.
Click to expand...
Click to collapse
Since the device is brand new as you implied, send it back for warranty. That would be the best thing to do, because chances are that even if you fix it after spending several hours on it, another issue might occur.
BTW factory reset screen is recovery mode. If you insist on keeping the device, let us know which kind of issues you are facing when trying to flash a .kdz.
vPro97 said:
Since the device is brand new as you implied, send it back for warranty. That would be the best thing to do, because chances are that even if you fix it after spending several hours on it, another issue might occur.
BTW factory reset screen is recovery mode. If you insist on keeping the device, let us know which kind of issues you are facing when trying to flash a .kdz.
Click to expand...
Click to collapse
Thanks for the reply, although it's brand new, it was bought on eBay so no can do about activating warranty and stuff.
Anyway, I tried a few more times fixing it, but gave up and put it in a lab.
I'll update next week, after it will return, what was the damage.
once again, thanks
Ice_machinE said:
Thanks for the reply, although it's brand new, it was bought on eBay so no can do about activating warranty and stuff.
Anyway, I tried a few more times fixing it, but gave up and put it in a lab.
I'll update next week, after it will return, what was the damage.
once again, thanks
Click to expand...
Click to collapse
The same like here
http://forum.xda-developers.com/lg-g2/help/strange-touch-behaviour-stock-rom-flash-t2922009
7547
rimaSamir said:
The same like here
http://forum.xda-developers.com/lg-g2/help/strange-touch-behaviour-stock-rom-flash-t2922009
Click to expand...
Click to collapse
I got the phone back from the lab and the technician told me that a screen digitizer is needed to be replaced.
Naturally, I told hime not to do that and I will send the phone back to HK to get a replacement phone.
Many thanks for everyone who tried to help me.
Ice
Hey guys,
I've bought my MX4 Pro almost a year ago, but decided only now to ask for your help. Hope you'll be able to guide me to fixing the several problems i have.
First of all, phone came with Flyme 4.5.7I and right from the start there were some features not working. Most important, the fingerprint screen unlock isnt working. After capturing my fingerprint, when i try to enable it to unlock screen it just takes me back to the home screen.
Another issue is getting sometimes (it happens randomly) a no sim error. Sometimes restarting is enough, sometimes i need to take out the sim card and insert it back.
Ever since i've tried to update firmware, hoping it would solve my problems. Nothing has worked.
Dowloaded the update.zip (no matter which version) and placed it in root directory. When i try to open it with the document app i get two options, view and extract. Can't update. Also starting the phone using volume+ and power button (update screen) has always produced the same results: Firmware corrupt. Tried doing it with clearing data, without that, no difference. Tried with a .bin file, same thing.
As far as i know the bootloader is locked, and i remember checking if the device is properly rooted and IT IS NOT.
So, the more android savvy people here can help? I'm lost and i really enjoyed the phone so far, but i dont really know what to do from now on. Is it a faulty device? (This would be the worse, since the phone was bought from China).
I can provide any additional details if needed.
Thanks in advance
P.S. I remember trying every tutorial/solution out there, nothing has seemed to work. I also may be dumb, not sure.
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