Hi all,
Before you jump at me telling me I haven't searched the forum, I DID and I couldn't solve my issue even with these solutions. To get you up to speed on what exactly I did.
Briefing (not very important):
I was doing my own business and I was free, I use my phone daily and it served me well. But I noticed that the last security patch I got was on 2020 and got me thinking. Why not just use custom ROMs to update my phone and get a year or two from my MIX3 (2018). I just recently flushed my brother's phone (Samsung) with a custom ROM and I liked it. I already installed TWRP 3 years ago on my brother's phone and I just had to install a zip file and boom new Android 12 on a 2014 phone.
The problem:
after reading here on the forums, it seemed that it is more complicated to do. I'm up to the challenge, I have done it before and the reward is worth it.
+Unlocking the Bootloader
this was a bit easy other than the connection issues but I got it unlocked eventually. (use the QR code to sign it. it is much easier)
I had an issue where after unlocking the bootloader the phone didn't allow me to install TWRP and do a backup, it immediately went into erasing the entire phone.
+Installing TWRP
I downloaded the files from TWRP website and everything was smooth other than the Mi Recovery popping every time I restart (install Magisk to plant TWRP then remove it if you don't need root)
+The downhill
after restarting, the phone worked fine I installed all the apps and restored everything. Afterward, I noticed that the camera does not work. It gives me an error. I reinstalled TWRP again since it was reverting to its Mi Recovery and I think here was the problem I flashed the recovery.img into the boot partition by mistake (I didn't notice at first) but after going back to the command I saw I made a mistake and reflashed the recovery with recovery.img and installed the Magisk and everything was ok. At the initial start, the SIM and the WIFI are not working.
after several attempts at reinstalling different flashable stock ROMs, I saw that the issue is consistent. I read online that you have five .img files that control the different parts of your phone. I got tired and decided to reflash the stock ROM via the Mi flasher and get it back to stock.
Even after flashing the stock ROM, I'm still having the same issue.
I reflashed the modem.img in the modem and still wifi and sim card are not working
I read that some phones have an A/B partition and my phone does NOT have it.
I'M AT A LOSS I CAN NOT FIX IT. IT'S BEEN 3 DAYS ON THIS AND I CAN NOT FIGURE IT OUT!!
Ok, If anyone was passing by I think I found what was the problem.
First, check if your problem matches mine. Go to Settings and check your IMEI. Or just dial *#06# ,if your phone did not return with a number then you lost your IMEI number.
follow this guide and I hope it helps. this is only for some phones so don't try it, it might break your phone
[GUIDE] Backup, edit and restore QCN. Fixing lost IMEI.
Introduction This is a guide to backup and restore the QCN, and to edit other's QCN in case you lost your IMEI and you don't have a backup of your QCN. There are other ways to do some steps (the most popular is via Fastboot) but I'm gonna...
forum.xda-developers.com
Related
Hello. This looks like the place I can get the best help.
Got a Xiaomi Mi5 last week - cheap and very cheerful. Having read online about possible fake roms and bloatware I thought the safest option would be to load the official stable rom to be safe.
Attempt 1
Following the MIUI guidance I downloaded the ROM, copied it to my phone in Windows explorer and then used the MIUI updater tool within the phone to load the new ROM.
http://en.miui.com/a-232.html
Everything went swimmingly for a couple of hours, but then the phone began crashing.
Attempt 2
By this stage I realised the above method was no longer available to me. So I got unlocking privalidges, unlocked my phone. Then, using MiFlash I flashed the latest ROM to the phone. Now the crashing problems happen within about a minute. It actually froze the screen first time round so I did it again.
Added fun issue - left my phone on overnight to charge. And it had stopped charging at 58%.
Attempt 3
Downloaded the EU MIUI Rom. Accessed TWRP in my phone and tried to use it to wipe and install. Not sure the wipes were fully effective - got a lot of red writing. And when I went to install the new ROM the internal storage was 0MB.
Had a look at guidance, and I forget what I did, but was finally able to see the zip file on my phone through TWRP. I got the "7" error. Have read how to fix this but seems too risky considering whats gone before.
Desired solution
I would just like any ROM on my phone which works. Don't really care which, I have followed each guide religiously. It may well just be a faulty phone but I don't want to send it back to China without ruling out the problem being me screwing with the software. Especially as I assume i've technically voided warranty... (I can reload Global Developer and relock it though so have hidden it pretty well. Only difference I can tell is that I now get a menu in recovery mode when before I got instruction to go to PCsuite).
Also - I seem to remember there originally being a downloaded_rom file in the internal memory which is no longer there. If im sending it back do I need to recreate one to hide my activity?
Appreciate any advice.
Moley1985 said:
Hello. This looks like the place I can get the best help.
Got a Xiaomi Mi5 last week - cheap and very cheerful. Having read online about possible fake roms and bloatware I thought the safest option would be to load the official stable rom to be safe.
Attempt 1
Following the MIUI guidance I downloaded the ROM, copied it to my phone in Windows explorer and then used the MIUI updater tool within the phone to load the new ROM.
http://en.miui.com/a-232.html
Everything went swimmingly for a couple of hours, but then the phone began crashing.
Attempt 2
By this stage I realised the above method was no longer available to me. So I got unlocking privalidges, unlocked my phone. Then, using MiFlash I flashed the latest ROM to the phone. Now the crashing problems happen within about a minute. It actually froze the screen first time round so I did it again.
Added fun issue - left my phone on overnight to charge. And it had stopped charging at 58%.
Attempt 3
Downloaded the EU MIUI Rom. Accessed TWRP in my phone and tried to use it to wipe and install. Not sure the wipes were fully effective - got a lot of red writing. And when I went to install the new ROM the internal storage was 0MB.
Had a look at guidance, and I forget what I did, but was finally able to see the zip file on my phone through TWRP. I got the "7" error. Have read how to fix this but seems too risky considering whats gone before.
Desired solution
I would just like any ROM on my phone which works. Don't really care which, I have followed each guide religiously. It may well just be a faulty phone but I don't want to send it back to China without ruling out the problem being me screwing with the software. Especially as I assume i've technically voided warranty... (I can reload Global Developer and relock it though so have hidden it pretty well. Only difference I can tell is that I now get a menu in recovery mode when before I got instruction to go to PCsuite).
Also - I seem to remember there originally being a downloaded_rom file in the internal memory which is no longer there. If im sending it back do I need to recreate one to hide my activity?
Appreciate any advice.
Click to expand...
Click to collapse
Greetings and welcome to assist. Xiaomi phones are encrypted by default so you need to wipe your phone in fastboot to access your storage again and you also need to flash latest su zip to disable dm verity. That should clear you internal memory issues and allow you to flash a zip through twrp
Good Luck
Sawdoctor
Hello,
I'll try to give all the details while keeping the long story short.
My moto C (xt1757) stopped working and I was forced to install again the stock rom. I never created a backup of the working phone before because I had no intention of flashing anything. But, when the problem occurred, the only thing I backed up, before starting, was the contents of /system/vendor/firmware.
Attempt 1. Custom ROM with TWRP.
Outcome: No flash was working using TWRP, all I got was a boot-loop.
Attempt 2. Custom ROM with SP Flash Tools.
Outcome: Again, boot-loops.
Attempt 3. Stock ROM with SP Flash Tools.
Outcome: Yet again, more boot-loops.
So, in the end, I decided to go the full monty with the phone and instead of just downloading the flash from the Stock ROM with SP Flash Tool, I used Format and Download instead. It worked :victory:, the phone was flashed and it booted.
I installed TWRP and rooted the phone again. All was happiness .
Until I noticed I was getting no signal from one SIM card :crying:. So I restored the backed up firmware (which was just the same thing from the stock ROM). Then I realized nvram stuff was deleted. At that point I didn't even knew what it was. So I did some research and was capable of creating the IMEI file MP0B_001 using two different tools, one was imei.386 from luckasfb's Fly_IQ255_Firmware_Build (here) and the other was the app GhostPhone (here).
I then noticed two more files in the same directory (/nvdata/md/NVRAM/NVD_IMEI/). These are...
MT00A001
MT00B001
at the beginning I just ignored them, however IMEI (IMEIs, actually, my phone is dual SIM) never changed from 000000000000000 to anything.
So at some point I decided to get rid of them, so I backed them up and delete them. Then voilà!, IMEI was being read correctly by Ghost Phone. However, android's IMEI information passed from 000000000000000 to empty. Also IMEI SV passed from 04 to empty.
So I tried to first set MP0B_001 and then upload MT00A001 and MT00B001. By doing that IMEI was again 000000000000000 and IMEI SV returned to 04.
Both files are identical, except for the file name, and both are binary. Nonetheless, some text is readble
Code:
LR9.W1444.MD.LWTG.MP WT6737M_65_Nn LWG_DSDS_COTSX
I suspect these two files act as a protection measure which prevents people from changing the IMEI. However, to the best of my knowledge, nobody has posted anything about them on the Net.
When I don't use those files, IMEI turns to "empty" according to android, even when Ghost Phone can read it properly (probably because it is just designed to decode MP0B_001) and WiFi MAC Address gets deleted (set as 00:00:00:00:00:00) every time the phone boots (/nvdata/APCFG/APRDEB/WIFI is rewritten by something). On the other hand, when I do use them, WiFi's MAC Address is OK but now IMEI becomes 000000000000000.
So I am kind of stuck here.
Any help will be appreciated.
I am a linux user, so I would thank you more if you don't rely on Windows apps; but I am open to suggestions.
My best regards.
This solved the issue for me. In a way, though.
Solution link
What is it? Well it is a working nvdata/nvram image that can be flashed using SP Flash Tools.
The important information here is the memory address where to flash nvdata.bin into my device (Moto C xt1557):
Code:
NVDATA=0x6b80000
The solution is posted for XT1756, but worked with my model too.
After flashing, both SIM cards were detected and WIFI MAC address was fixed. It was no longer 00:08:22:XX:XX:XX, but d0:04:01:XX:XX:XX. (Which is a valid vendor for the device: Motorola Mobility LLC, a Lenovo Company)
IMEI is obviously not my IMEI, but phone is working. So I will eventually find a way to change it.
After flashing I lost root, but TWRP image was intact, so I recovered ir fast.
Hope this helps somebody or myself in the future.
Good day,
Help is needed..
I flashed TWRP on the phone since it was not long ago updated to version 10.3 (China).
It flashed well (without errors).
The reboot was successful. No data was lost.
In the morning I decided to check the email, turned on the WIFI, and it went off after 2-3 seconds (everything was OK in the evening, it worked like usually). I thought that restarting the phone would fix the flaw, but alas, I was stuck in BOOTLOOP. Starts with the Mi. LOGO, then goes out, then shows again and goes into Recovery. Recovery runs. All data can be accessed. Restarting is possible only into RECOVERY and FASTBOOT.
What could be the snag here and how to solve it?
P.S. Have tried 'dirty flashing' 10.3 and 10.2 versions from TWRP, changing the kernel (androplus 7-9), reflashing Magisk (recommended by some users on a russian forum), recovering the boot.img (since it it the only recovery I have got).. All that to no avail.
Bootloader was always unlocked since I bought it and rooted. It was MIUI v10.0 then.
MI MIX 3 8/256
Stable 10.3 Chinese ROM with twrp (10.2 before update, with root and twrp)
Had no root but unlocked bootloader
z1ldj1an said:
Good day,
Help is needed..
I flashed TWRP on the phone since it was not long ago updated to version 10.3 (China).
It flashed well (without errors).
The reboot was successful. No data was lost.
In the morning I decided to check the email, turned on the WIFI, and it went off after 2-3 seconds (everything was OK in the evening, it worked like usually). I thought that restarting the phone would fix the flaw, but alas, I was stuck in BOOTLOOP. Starts with the Mi. LOGO, then goes out, then shows again and goes into Recovery. Recovery runs. All data can be accessed. Restarting is possible only into RECOVERY and FASTBOOT.
What could be the snag here and how to solve it?
P.S. Have tried 'dirty flashing' 10.3 and 10.2 versions from TWRP, changing the kernel (androplus 7-9), reflashing Magisk (recommended by some users on a russian forum), recovering the boot.img (since it it the only recovery I have got).. All that to no avail.
Bootloader was always unlocked since I bought it and rooted. It was MIUI v10.0 then.
Click to expand...
Click to collapse
Back up, wipe, flash, restore
Ok. That was the one thing I tried to avoid, since my backup is 27G (nandroid) and internal storage is 133G..
Will try and feedback.
Hi all,
Got it back again, of course with all data and apps gone. I have done nandroid backups (since there is no other way of backing things up from TWRP, except copying everything) from recovery before starting the upper described process. I figure they are of no use to me now or are they?
Please advise
P.S. restoring from nandroids brought me back to square 1..
z1ldj1an said:
P.S. restoring from nandroids brought me back to square 1..
Click to expand...
Click to collapse
Something not right with your data so start over
Restarted, redone. Recovered only Data. Looks ok but works a little laggy..
Upd.: needed to set up the screen lock after had done that and a restart, all works like it was, except with a new OS version
Install TWRP from xiaomi.eu, the official one from here seems to be a lot more buggy.
Isopropil said:
Install TWRP from xiaomi.eu, the official one from here seems to be a lot more buggy.
Click to expand...
Click to collapse
I took it from twrp themselves, not bothering to search any forums. It's not like digging for gold or the like
Upd.:
I read that the official TWRP doesn't support some mounts migrating from EU to global or CN-->EU V Global. It was discovered that it has some bugs with mounting paths. People recommend the LR Team TWRP over the official because of that, besides it has more options under Advanced tab e.g.
Personally I prefer the one that does the job for the moment and is the latest, so it was an easy choice for me ? especially installing a fresh OS update.
Hi and thanks in advance for any help anyone can provide, I think my phone is dead :crying:
Anyway, story time...
I woke up to the door knocking and the postman was there with a package I had to sign for. My heart jumped as I knew it was my new OP6 from ebay (refurbed and from a highly regarded refurbed phone seller).
I inserted my SIM and the symbol for signal came on so the sim slot was working. I then connected to my wifi so the wifi is working. I like to customize my phones so I immediately come to XDA to find a ROM I'd like to install and to find the instructions for unlocking the bootloader, installing TWRP and Majisk. I looked and settled on AOSiP seeing that the required OOS firmware is 10.3.0 I upgrade through the system update feature.
Having updated I go on to unlock the bootloader, install TWRP and magisk. Upon unlocking the bootloader when the system rebooted it stopped reading sim cards and picking up wifi signals. Using adb I installed TWRP (using the proper method of temporarily booting into the TWRP and the installing the ZIP. Like an idiot I didn't read the instructions properly and flashed the AOSiP zip which failed.
I thought the best thing to do was start over so I flashed the official recovery boot image using adb. I ended up only able to access the bootloader/fastboot. Every option apart from turn off just caused the phone to boot into the bootloader. I fixed this using the instructions on https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 using the 10.0-OnePlus6Oxygen_22_OTA_040_all_1910270546_42a63-FASTBOOT.zip and I can now access the system but the setup keeps stopping and it still won't pick up sim cards or wifi and keeps rebooting.
I have tried to restore to stock using the system update feature and manually downgrade but the phone reboots before the downgrade gets chance to finish. I think this is eveything I did although maybe I pressed something i shouldn't have in TWRP.
I've heard two different things about this issue one is that android 10 is not fully working yet and that's causing the reboots and connectivity issues but I have had an OP6 before (I had to sell it ) another thing I heard was it was a hardware issue and the motherboard needs replacing. Please help, if it is a software issue then I'm screwed, I relocked the bootloader but I'm sure the seller will be able to tell and not replace of refund the item. If it's a hardware issue I can at least get my money back. If anyone can help me fix this it would be much appreciated.
Hi all
I have a bit of a problem after flashing the Google GSI (android 13) on my Lenovo Tab P11. Everything seemed to work well. Rebooted into the OS without any issues, everything seemed to work (Wifi included). I then swapped and deployed LineageOS 20 GSI which again, seemed to go okay but I had a google play protect issue.
During a quick check, I was planning on just rolling back to the Google GSI one, but accidently locked my device with
./fastboot.exe flashing lock
instead of unlock. And, taking no notice of the on screen prompts proceeded to relock the device which effectively bricked it. Nothing would load, not even recovery or fastboot.
A fair while later I managed to get recovery/fastboot working again by redoploying the boot.img, recovery.img and vbmeta.img from the stock ROM. I then discovered my current-slot had changed from b to a, so swapped that back too. This allowed the device to at least go into fastbootd so I ccould reflash it. I put the LineageOS back on, but now Wifi isn't working. Rolled back to Google GSI and the same.
I've tried following guides to re-install stock, but that's failing as well. I have read a couple of posts detailing issues with Wifi on GSI but the fixes didn't do anything or weren't necessarily inline with what I had. I suspect I have missed something I need to push back out to the device, but at this point I'm a bit stuck.
Anyone came across this before, or can point me where I can get some more information on it?
ta
whether some partitions are deleted or corrupted. You have the original backup qcn . try restoring it or trying to fix the partitions