Related
Hello there,
Today I will teach you how to make a full backup of your Spreadtrum phone !
This tutorial may also work on several other phones.
CWM can make a nearly full backup of your Spreadtrum, but it's not enough unfortunately.
Android is compartmented in 4 main partitions. You have theses partition:
* boot - It contains the Linux kernel
* System - It contains Android
* Recovery - It contains the recovery system, CWM if you installed it.
* DATA - It contain your personal datas, and should not be published online if you share your backup online.
But Android is one thing, your phone also have a lot of bios, firmwares, and bootloaders. Theses are not saved by traditional backup utilities such as CWM.
Theses partitions includes:
* UBoot - Very important, this thing is the low level bootloader. It starts Linux !
* Modem Firmware - used to dial with your GSM provider
* DSP Firmware - Make video playback smoother using DSP resources.
* NV - It's some kind of encryption key with some low levels parameters. Very important !
* Lots of misc stuffs - Like the boot logo, the kernel panics logs (record the boot-up errors to help the debugging process), etc ...
* Lots of important misc stuffs - For example what start-up the device even before handing the phone to Uboot.
This thread will cover a new way to backup your device, working "only" on rooted Spreadtrum devices.
With this you can recreate your original firmware file, and then rescue your phone even on the worst case you can find. (And help those with the same phone as you but have made a big flashing mistake)
So first, you will need to root your device. It may be simple or difficult, it all depends of the device you have. The instructions on how to root your device are here: http://forum.xda-developers.com/showthread.php?t=2165554
When you are rooted, you will have to install the Spreadtrum drivers if it's not already the case and log into your device with ADB.
You can download the drivers here:
http://www.mediafire.com/download.php?c5nf3rlhxmxhu4x
http://www.mediafire.com/download.php?2tyg0k2xp3ejgyg
You can download ADB and learn how it work here: http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Then you will have to tell adb what phone to use. By that I mean adding the PCI ID to a text file to tell adb that this peripheral is compatible.
The Spreadtrum PCI ID is 0x1782
add this line to "Your user directory/.android/adb_usb.ini"
Code:
0x1782
So when you are ready to go, you have to download this file: http://www.mediafire.com/download.php?y6wmegkc22gkr97
Then with adb, push it on your device with this command:
Code:
adb push backuptools.tar /data/local/tmp
Now we will extract the tools with this command:
Code:
adb shell su -c "tar -xvpf /data/local/tmp/backuptools.tar"
And now, let's start the backup process:
Code:
adb shell su -c "./mkbackup.sh"
and here we go, just wait a while and every partitions on your phone will be saved in the backup directory on the sd card !
You will never have to backup this way again as those partitions are read only, if you don't do crazy things they will never change. But if you want to make another backup I suggest you go with CWM (read this page if you don't have it: http://forum.xda-developers.com/showthread.php?t=2165554).
Please do another backup with CWM even if everything as gone right with this method. Just to double check !
PS: if CWM does not work for you, you just have to send me your boot.img file from your backup and I will make one compatible with your phone.
To restore your backups you will also need to have CWM, you also can use ResearchDownload if you manage to entirely brick your phone or if any attempts to make a CWM recovery fails. I will have to do a tutorial about that too.
Thanks a lot :good:
this is my boot.img after a full backup :www .mediafire.com/?gmnm65rn65b28c3
i need a CWM image for my GT-I9300 clone.
all the best.
monster-exodia said:
Thanks a lot :good:
this is my boot.img after a full backup :www .mediafire.com/?gmnm65rn65b28c3
i need a CWM image for my GT-I9300 clone.
all the best.
Click to expand...
Click to collapse
Hi,
Can I have the exact name of your device ? (it must be in the battery compartment)
Did you tried all the CWM already in the rooting tutorial ? (I added one this morning)
If none of them work, I made this recovery with the boot.img you provided: http://www.mediafire.com/download.php?aj2nman38j5cfip
Please don't forget to tell me what CWM work for you so I can add the name of your phone on the tutorial.
@ElectronikHear
phone model (in battery) : N9300
phone model : (system info) GT-I9300
Build number : MT6515M_C909_HT_V14
cpu hardware : SP6820A
..........
I never tried ... firslty how to to flash CMW recovery ?
thanks in advance.
deleted
monster-exodia said:
how to to flash CMW recovery ?
Click to expand...
Click to collapse
Well it's explained in the rooting tutorial.
If your phone have Fastboot you can flash using it. If you don't you can use the Spreadtrum flash utility called ResearchDownload.
Everything is here:
http://forum.xda-developers.com/showthread.php?t=2165554
As your phone is already rooted it will be a lot more simple to flash using "dd" or some android flashing utilities. Actually it doesn't work that way on theses phones, sorry ... So just do as the rooting tutorial explains.
Hi, I'm succesfully rooted my phone with the "rooted system partition image" method, but none of the CWM images work, so I would be grateful if you can send me the recovery image.
Device Info:
Phone model (in battery) : S6500-TV
Phone model : (system info) S560
Android Version: 4.0.3
Baseband Version: DM_BASE_12A_W12.32|sc8810_modem|08-9-2012 16:47:10
Kernel Version: 2.6.35.7 [email protected] #3
Software Version: T162_JYY_G2_P2_1_W1220P12_DNY_V0.8.1_20121015
Hardware Version: 1.1.0
boot.img : www .dropbox.com/s/ka43sd45em9lu9k/mtd9.boot.img
Thanks in advance.
monster-exodia said:
I never tried ... firslty how to to flash CMW recovery ?
thanks in advance.
Click to expand...
Click to collapse
Don't even try!
Backup first.
janzlev said:
Hi, I'm succesfully rooted my phone with the "rooted system partition image" method, but none of the CWM images work, so I would be grateful if you can send me the recovery image.
Device Info:
Phone model (in battery) : S6500-TV
Phone model : (system info) S560
Android Version: 4.0.3
Baseband Version: DM_BASE_12A_W12.32|sc8810_modem|08-9-2012 16:47:10
Kernel Version: 2.6.35.7 [email protected] #3
Software Version: T162_JYY_G2_P2_1_W1220P12_DNY_V0.8.1_20121015
Hardware Version: 1.1.0
boot.img : www .dropbox.com/s/ka43sd45em9lu9k/mtd9.boot.img
Thanks in advance.
Click to expand...
Click to collapse
Hi there,
Here is your new recovery: http://www.mediafire.com/download.php?iahnncpjhm44etn
Please tell me if it works so I can add it to the rooting tutorial ^^
Thank you very much !
Not working, after flashing the recovery, the phone enters into a boot loop.
Anyway thank you.
janzlev said:
Not working, after flashing the recovery, the phone enters into a boot loop.
Anyway thank you.
Click to expand...
Click to collapse
A boot loop ?
You mean the recovery is looping ? and if you try to boot as normal everything working ok ?
I don't know what has gone wrong ... Where did you find your boot.img ? Did you extract it from the rom as the tutorial said or extracted from a .pac file ?
Have you flashed it with fastboot or with ResearchDownload ?
ElectronikHeart said:
A boot loop ?
You mean the recovery is looping ? and if you try to boot as normal everything working ok ?
I don't know what has gone wrong ... Where did you find your boot.img ? Did you extract it from the rom as the tutorial said or extracted from a .pac file ?
Have you flashed it with fastboot or with ResearchDownload ?
Click to expand...
Click to collapse
Recovery does not start, normal boot enters into a boot loop, the boot.img is extracted from the rom as in the tutorial.
Flashed with ResearchDownload.
janzlev said:
Recovery does not start, normal boot enters into a boot loop, the boot.img is extracted from the rom as in the tutorial.
Flashed with ResearchDownload.
Click to expand...
Click to collapse
That's weird, really weird. Because the recovery partition is not involved in the normal boot procedure. So flashing a new recovery should not harm in any way the normal boot procedure.
I really don't know what have brought your phone in such state I'm afraid.
Maybe you should try to flash the recovery again. and see if everything is the same.
As the recovery is not involved in the normal boot process, it surely will not change anything, but as you have tried the over ones (CWM I mean), and that have not screwed your booting process, you may try to flash one of the non working ones again (but known for sure to not harm the boot process) to see if it work again.
Have you used the same FDL set as when you flashed the system partition and the over CWM ?
It's a good thing you have the full backup on your hand. Because you may surely be able to recover from that. I just have to make a tutorial about flashing the backup with ResearchDownload and explaining what file goes where from the backup.
ElectronikHeart said:
That's weird, really weird. Because the recovery partition is not involved in the normal boot procedure. So flashing a new recovery should not harm in any way the normal boot procedure.
I really don't know what have brought your phone in such state I'm afraid.
Maybe you should try to flash the recovery again. and see if everything is the same.
As the recovery is not involved in the normal boot process, it surely will not change anything, but as you have tried the over ones (CWM I mean), and that have not screwed your booting process, you may try to flash one of the non working ones again (but known for sure to not harm the boot process) to see if it work again.
Have you used the same FDL set as when you flashed the system partition and the over CWM ?
It's a good thing you have the full backup on your hand. Because you may surely be able to recover from that. I just have to make a tutorial about flashing the backup with ResearchDownload and explaining what file goes where from the backup.
Click to expand...
Click to collapse
Thanks would be really helpful, and yes I used the same FDL.
janzlev said:
Thanks would be really helpful, and yes I used the same FDL.
Click to expand...
Click to collapse
I made another CWM recovery for your phone, please try it: http://www.mediafire.com/download.php?lg7m6v49efzpnjk
Apparently was an error of ResearchDownload (It seems was flashing recovery.img into boot.), so I tried with another copy of ResearchDownload and FDL files and now works like a charm.
Thank you very much!
janzlev said:
Apparently was an error of ResearchDownload (It seems was flashing recovery.img into boot.), so I tried with another copy of ResearchDownload and FDL files and now works like a charm.
Thank you very much!
Click to expand...
Click to collapse
Can you tell me what version of ResearchDownload have this bug. It's a pretty scary one. I have to be sure I don't have it on my computer ...
By the way what CWM image is working ? The first or the second one ? (the two should work but I want to be sure before adding it to the main tutorial)
Thank you very much ! That's one more phone to the list of easily rootable Spreadtrums thanks to you !
Edit: And what FDLs you use precisely so I can rename the folder to reflect the use of this set for this phone (Is this the ones on the .pac firmware you've uploaded on the over topic ?)
RESEARCHDOWNLOAD R2.9.6010, with the R2.9.7002 everything's fine. Respect to the CWM images, after the error I tried with the second one, so maybe the first one also works, the FDLs that I used was extracted from the .pac dropbox.com/s/69yl8hn9361qpy5/FDLs-S6500-TV.tar
That's it, if I can help more, let me know.
janzlev said:
RESEARCHDOWNLOAD R2.9.6010, with the R2.9.7002 everything's fine. Respect to the CWM images, after the error I tried with the second one, so maybe the first one also works, the FDLs that I used was extracted from the .pac dropbox.com/s/69yl8hn9361qpy5/FDLs-S6500-TV.tar
That's it, if I can help more, let me know.
Click to expand...
Click to collapse
I think I have every informations I need ^^
I have added the recovery for S6500-TV to the main tutorial and will add in a short while the fdls to the FDL pack file.
Thanks again !
Backup
attached is my boot.img
to follow: entire backup
So as a fan of Android and ICT literate I decided to root, new recovery and install a new ROM to get my favourite MediaPad M2 8.0 LTE as stock Android as possible.
I unlocked the bootloader, installed TWRP successfully and it works.
However on my haste I messed up my android ROM install. No problem: got TWRP, just find a new stock ROM to install except unlike my phone it seems it's not that simple with this tablet?
I'm picking up that you cannot install a true stock Huawei ROM without losing TWRP. Not great but okay.
Downloaded a stock ROM, used Huawei extracter to pull the recovery IMG and flashed via TWRP.
Booted up and it goes straight to Huawei's own fastboot screen and Huawei's own software won't recover.
I've flashed TWRP back again for now.
So I basically need a ROM I can install from fresh which will install via TWRP.
Am I right that the official Roms are out due to the recovery requirements?
Have I missed something obvious to get this tablet alive again?
TheOnlyPaulV said:
So as a fan of Android and ICT literate I decided to root, new recovery and install a new ROM to get my favourite MediaPad M2 8.0 LTE as stock Android as possible.
I unlocked the bootloader, installed TWRP successfully and it works.
However on my haste I messed up my android ROM install. No problem: got TWRP, just find a new stock ROM to install except unlike my phone it seems it's not that simple with this tablet?
I'm picking up that you cannot install a true stock Huawei ROM without losing TWRP. Not great but okay.
Downloaded a stock ROM, used Huawei extracter to pull the recovery IMG and flashed via TWRP.
Booted up and it goes straight to Huawei's own fastboot screen and Huawei's own software won't recover.
I've flashed TWRP back again for now.
So I basically need a ROM I can install from fresh which will install via TWRP.
Am I right that the official Roms are out due to the recovery requirements?
Have I missed something obvious to get this tablet alive again?
Click to expand...
Click to collapse
First of all, I'm not sure whether flashing the official Huawei partition images will work if they are flashed from TWRP (I've never tried it). However, I do know that it works without problems when flashed in fastboot mode. Secondly, if TWRP was flashed as the recovery and you chose the TWRP inbuilt root option, it would have replaced your BOOT partition as well. So to repair this, you'd have to flash the official Huawei BOOT partition as well. BTW, I was in a similar state (bootloop/no boot) a couple of times (see my post here) and both times was able to recover by flashing the official Huawei BOOT.img and RECOVERY.img partitions to my device.
So, to get your device back into a decent shape, try flashing the BOOT.img as well as the RECOVERY.img from the official Huawei ROM for your device, performing the flashing in fastboot mode. I have written a guide which details extracting and flashing official Huawei partitions. Best of luck
It is obvious that I am missing something very simle here and I'm very interested in finding out what it is I'm doing wrong
So I have a TWRP booting tablet.
I downloaded the latest image from the roms thread on this forum which gives me a zip file called "M2-801LC100B205.zip".
I extract this and open it in Huawei extracter tool.
I extract the BOOT, RECOVERY, SYSTEM and CUST to separate .img files.
I flash all 4, one after the other using the commands listed in your guide:
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
They all flash okay (it seems), an exmaple of the flash is:
C:\platform-tools>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (454239 KB)...
OKAY [ 17.471s]
writing 'system' 1/6...
OKAY [ 5.909s]
sending sparse 'system' 2/6 (449072 KB)...
OKAY [ 16.927s]
writing 'system' 2/6...
OKAY [ 5.788s]
sending sparse 'system' 3/6 (459356 KB)...
OKAY [ 17.035s]
writing 'system' 3/6...
OKAY [ 5.894s]
sending sparse 'system' 4/6 (442527 KB)...
OKAY [ 17.781s]
writing 'system' 4/6...
OKAY [ 5.713s]
sending sparse 'system' 5/6 (447342 KB)...
OKAY [ 20.828s]
writing 'system' 5/6...
OKAY [ 5.736s]
sending sparse 'system' 6/6 (67700 KB)...
OKAY [ 2.524s]
writing 'system' 6/6...
OKAY [ 0.864s]
finished. total time: 122.498s
C:\platform-tools>
But still I have a tablet that is stuck on the boot screen. I can still get back to the fastboot recovery so I can still flash but I seem to be missing WHAT to flash?
Surely there must be a complete .img file some where I can flash in flash boot which will just get the thing back and working?
It seems like I'm flashing lots of small simple things when I just want a complete image from some where to flash?
I cant flash the downloaded zip files via fast boot it seems?
Does one exist of have I missed some thing?
Update:
I downloaded a ZIP file of a full rom as detailed above, installed TWRP and tried to flash the zip: it fails stating it could not mount the system partition and radio firmware does not exist. I assume this is because the file downloaded is an update and not a complete rom?
I used TWRP to format and resize the system partition and it reports 0mb in size and fails.
I really think I just need a plain original simple complete rom to flash, in a ZIP format for TWRP: the updates all seem to assume its being flashed onto a working system as an update and I don't have a full base install.
Surely this base simple rom must exist some where?
Any one?
Next step for this tablet is to return it unfortunately as I'm totally beat
Does any one have a TWRP backup I can flash for a media pad m2 lte 8.0?
TheOnlyPaulV said:
Any one?
Next step for this tablet is to return it unfortunately as I'm totally beat
Does any one have a TWRP backup I can flash for a media pad m2 lte 8.0?
Click to expand...
Click to collapse
Hmmm... I expected you to only flash the boot and recovery images as mentioned in my previous reply (and not other partition images, the example text in my guide was just that - an example) from your original ROM version, not from a downloaded ROM version. If your original ROM was a lollipop ROM and not marshmallow, B205 is a mm ROM and would require a full ROM flash, and in this case a bits-and-pieces flash would not work, and cause a non-booting device. A bits-and-pieces flash especially of any device partition other than BOOT and RECOVERY should ideally be done only with the ROM version which is currently installed and (previously known to be) working.
If you can connect the phone to your computer long enough to transfer over the full ROM image to the device, you should be able to flash that using the original Huawei recovery. The instructions are present on the forum thread where you found the ROM. Alternatively, if you know what version the original ROM was on your device, you can flash its SYSTEM and CUST over.
Yes, that's what I would like to do and I can do that, fast boot still works, but it's where do I get a FULL ROM from? Everything on this forum I have found is an update and relies on another working ROM to be present.
Where do I get the full ROM from, do we know the name of one which is not an upgrade ROM?
It's this full ROM I've been looking for to no avail
Please confirm your device model and I'll try to find a full ROM image download (Marshmallow) for you.
EDIT: by full I mean a ROM which is a complete image (about 2-3GB) instead of a partial OTA update. Also, I'm not certain that you can flash a full Huawei official ROM image from fastboot; it requires booting into the recovery. AFAIK Booting into the recovery does not need a working ROM system partition.
Thanks for this! So as I cannot get into android, I've looked on the physical back of the device and it says it's a m2-801L. I purchased a Huawei MediaPad 8.0 LTE. I can flash the Huawei standard recovery and boot fine, I can flash from that and have tried to flash parts of Roms from that so I assume a full ROM is a similar process?
Also would a full TWRP backup also not work?
Thanks again for all your help however, I'm happy to buy you a beer (or non alcoholic beverage of your choice!l
Sorry to bug but have you, or any one else, had any luck in finding a full rom?
Any one have a twrp backup of a basic fulll booting rom I could try?
I do appreciate all the help!
TheOnlyPaulV said:
Thanks for this! So as I cannot get into android, I've looked on the physical back of the device and it says it's a m2-801L. I purchased a Huawei MediaPad 8.0 LTE. I can flash the Huawei standard recovery and boot fine, I can flash from that and have tried to flash parts of Roms from that so I assume a full ROM is a similar process?
Also would a full TWRP backup also not work?
Click to expand...
Click to collapse
Sorry for the delayed reply, I've been pretty ill for the last few days.
Here are links to what I'm pretty certain are the OEM Lollipop full ROMs for the 801L. All those links are 1.4GB zipped, which means that they should unzip to about 2.5-3GB, which indicates that it is a full ROM:
801L B006 on Huawei Malaysian support site: http://download-c.huawei.com/download/downloadCenter?downloadId=57706&version=181649&siteCode=my
801L B007 on Huawei Malaysian support site: http://download-c.huawei.com/download/downloadCenter?downloadId=71503&version=254039&siteCode=my
801L B003 on Huawei Russian support site (): http://download-c.huawei.com/download/downloadCenter?downloadId=71523&version=254048&siteCode=ru
You'll need to get the unzipped ROM folder onto your external SD card somehow, to be able to flash it with the Huawei recovery.
Here are some steps you can follow:
Part 1: Download ROM, extract it and then copy extracted ROM directory to sdcard on phone
In this part, we will download the ROM, extract it, and transfer the extracted ROM to your M2 using TWRP and ADB. Make sure that you have the Mediapad drivers installed, and adb and fastboot installed and available.
If you're on Windows and need the ADB and fastboot binaries, you can install the "15-second ADB installer" found in this thread.
On Linux, just install the Android Command Line tools from Google.
For the phone drivers, just install HiSuite from Huawei - this will install the Mediapad device drivers. You can then uninstall HiSuite - the drivers will still continue to remain installed even if HiSuite is uninstalled, and this way you won't clutter up your computer with the useless HiSuite.
Now download one of the ROMs listed above (I suggest starting with B007. If that doesn't work, try B003 and then B006).
Unzip the downloaded ROM onto some location on your computer's hard drive. Let's say that on Windows, you unzip it to D:\MYROM
In D:\MYROM, you should find a directory called dload
Make sure that you have TWRP as the recovery on the phone. Flash TWRP onto the phone if you need to (since you already know how to do this, I won't go into more detail).
Boot into the TWRP recovery on the phone (since you already know how to do this, I won't go into more detail).
In TWRP, make sure that MTP mode is off. To do this, in the TWRP main menu, press "Mount". In the "Mount" screen, check whether the second (right-hand-side) button on the bottom reads "Enable MTP". If it says "Enable MTP", then you do not need to do anything else here, go back to the main TWRP screen. If the button says "Disable MTP", press it so that the button now reads as "Enable MTP". Setting MTP mode off will ensure that you can connect via ADB to your phone.
Now open a terminal/command-prompt window on your computer (Run->"cmd" or search for "cmd" on Windows).
In the terminal window, navigate to the directory where the unzipped ROM is present. On Windows, using the above example ROM unzip location, you would type
Code:
d:
cd D:\MYROM
Type the following ADB command to make sure that your phone is recognized by ADB:
Code:
adb devices
If it works, you should see something like
Code:
List of devices attached
ABCD1234567890 recovery
where "ABCD1234567890" will actually be your device ID string, and not literally "ABCD1234567890"
If you see a string like the above, good news, it means that your phone is recognized by ADB, and we can now transfer the unzipped ROM to your SD card. If you do not see anything after the "List of devices attached" string, make sure that you have turned off MTP mode in TWRP as detailed above. If you still don't get anything, you will have to transfer the unzipped ROM to your sdcard by some other means - perhaps by putting the SD card in another phone. Skip the rest of the steps here and see Part 1.5 below.
Now type the following command in your computer's terminal window (command below is for Windows; on Linux, replace "D:\dload" with the appropriate path to the dload directory):
Code:
adb push D:\MYROM\dload /sdcard
This will copy the extracted ROM's "dload" directory to the root of your internal SD card. To copy it to the root of your external SD card, replace "/sdcard" in the above command with "/external_sd".
If all went well with the above command, then at this point your extracted ROM's "dload" directory should have been copied over from your computer to your phone (either on the root of the internal SD if you used "/sdcard" in the "adb push" command, or on the root of the external SD if you used "/external_sd" in the "adb push" command. Go to Part 2 below.
Part 1.5: Copy extracted ROM directory to external sdcard on phone using another phone.
SKIP THIS PART IF YOU SUCCESSFULLY COMPLETED ALL STEPS IN PART 1 ABOVE, AND GO TO PART 2 BELOW!
Remove the external SD card from your M2.
Insert the external SD from the M2 into some other phone/device.
Connect that phone to your computer via USB.
Transfer the unzipped ROM's "dload" folder to the root of the SD card.
Remove the SD card from the other phone and put it back into your M2.
Part 2: Flash official Huawei BOOT.img and RECOVERY.img and installed extracted ROM using official Huawei Recovery
In this part, we will replace TWRP with the official Huawei recovery and boot partitions, and use the official Huawei recovery to flash the ROM on the phone.
From the ROM you downloaded in Part 1 above, extract BOOT.img and RECOVERY.img using the Huawei Update Extractor. Since you already know how to do this, no further details will be given.
Flash the official Huawei BOOT.img and RECOVERY.img partitions (for safety, do not flash any other partitions) onto your M2. to refresh your memory on how to do this, see my guide.
After successfully flashing the official Huawei BOOT.img and RECOVERY.img partitions to your M2, you can flash the downloaded ROM as an update by booting into the Huawei recovery which you just flashed onto your M2. After booting into the Huawei recovery, it should automatically detect and start installing the downloaded ROM.
Hope this helps. Good luck!
TheOnlyPaulV said:
Thanks again for all your help however, I'm happy to buy you a beer (or non alcoholic beverage of your choice!l
Click to expand...
Click to collapse
That won't be necessary, but thanks for the offer I'm just trying to help out people wherever I can; I don't want anything in return
Hello, "different customer" here
I came into the same situation, a while ago I wiped a lot of things (through TWRP) making my tablet unbootable, I was trying to recover from a bootloop.
I followed this well written guide but the stock recovery won't detect the new ROM (I have a dload folder with META-INF directory inside and UPDATE.APP).
I flashed the BOOT.img and the SYSTEM.img while at fastboot mode. At the sdcard there is a folder dload with the rest.
Booting up with pressed + and - is starting to "Installing update" but hangs at 5%
What should I do
Well finally I managed to fix it, twice! here is the story.
After I left it for half an hour saying "Installing update 5%" I decided to reboot.
Tablet booted ok but there was problem with WiFi, couldn't switch to On.
I decided to reflash http://update.hicloud.com:8180/TDS/d...1LC100B206.zip once again but still nothing, I tried B002, B005 but no success with the WiFi (this wifi problem is something I did when I was fing around at the bootloader with fastboot).
Then I decided to flash the SimplyGoogle, that got me in a bootloop.
Ok I said now I will fix it once and for all.
Then I entered TWRP, wiped EVERYTHING and I got this http://update.hicloud.com:8180/TDS/d...1LC100B206.zip uploaded to the /sdcard/dload.
Next step was fastboot mode, flashed BOOT.img, System.img and recovery.img from the extracted UPDATE.APP of the M2-802L once again (keep in mind I have the M2-801L).
Now it was time to poweron with + and - pressed so the recovery to understand I need a system update/flash.
Again it was stuck at 5% but now I knew just left it hanging for an hour and rebooted.
And it worked.
At this point I want to give a big thanx to beast.in.black for his awesome instructions for how to recover a dead tablet.
lepidas said:
At this point I want to give a big thanx to beast.in.black for his awesome instructions for how to recover a dead tablet.
Click to expand...
Click to collapse
You're welcome, glad I could be of assistance
Your posting of your experiences may help someone else who runs into a similar issue, so thank you for taking the trouble to post in detail :good:
Im afraid I am not quite as advanced as your self, I dont know what a 'META-INF directory inside and UPDATE.APP' is so please bear with me, especially if im preaching to the converted.
My problem was that I had a, basically, blank device.
The only thing that remained was the boot and recovery.
The first thing I got wrong is that the device is partitioned into multiple parts, its not one rom image for it all thus flashing a update rom wont write over all the partitions to recover the device, it will only flash the ones its updating thus you need an image that has alll the partitions to recover from a wiped device.
Second problem I has was that the TWRP recovery will not allow flashing of complete roms and I didnt have a backup of a complete rom.
Third problem I had was getting a hold of a 'complete image'.
So the link above allow you to download a complete image. part1 done.
then extract the boot partition from the complete image as the complete rom will only install/boot from its own boot partition: you cant install a complte from from a TWRP partition.
flash the bootimage from the complete rom.
copy it to the SD card, install it from there.
Then, once you have your system up and running, install your updates ot get the unit back.
Hope that makes sense and ive not just repeated things you already know, but thats as far as my knowledge goes
I've noticed that many in this forum for the Honor 7x / Mate SE want to try a few ROMS, and then eventually go back to stock - Some just want to go back to stock. I had my own issues and thankfully there were others to help along the way. This method does not use fastboot to flash partitions, it uses TWRP, so the assumption is you have a working TWRP. Also I am not responsible for any bricks, I am just explaining what I did to get back to stock (And based on all the issues people are having, I'm staying there)
If you've tried a Treble ROM or others, the route I took to get back to stock was as follows:
1.) Download your firmware from Firmware finder or the Pro-TeamMT website:
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-l34&firmware_page=0
In this example, mine is the Mate SE..
You should have downloaded 3 files. The important one we want right now is the Update.zip - Extract this file. You should see UPDATE.APP within this folder.
2.) Download the Huawei extractor software by worstenbrood:
https://forum.xda-developers.com/showthread.php?t=2433454
3.) Use this software to extract the files from the Update.App - You may need to disable the Checksum checks under "Settings". When you select the UPDATE.APP file, you should get a list of the files that are compiled or compressed into the app. The main 4 files you want are Ramdisk, Vendor, System, and if you'd like the Stock recovery (Recovey_Ramdisk). Copy these files to your SD card.
4.) Assuming you still have the functioning TWRP, reboot into TWRP and wipe everything but the SD card.
5.) Flash the images to the appropriate partition, Ramdisk = Ramdisk, Vendor = Vendor Image, and System = System Image - Ensure you're flashing the image partitions. Ramdisk is necessary if you've ever rooted or used Magisk.
At this point you should be able to reboot and get back into stock...But you'll notice Themes do not work properly..That's because you've wiped / formatted data at some point in TWRP, and now the Data/hw_int has been wiped. You can fix this by flashing the update on top of itself by the instructions in this thread (Thanks to mrmazak):
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
See the "Flash update while on Oreo"...This has worked twice now to get me back my themes after wiping /data.
I counted on my TWRP backup to get me back to stock after trying a Treble ROM, and I ended up bricked. So hopefully this helps someone!
PS, if anyone has more to add this this, the more help the better.
Wait, wouldn't the recovery be the file "RECOVERY_RAMDIS.img"
???
crayonicle said:
Wait, wouldn't the recovery be the file "RECOVERY_RAMDIS.img"
???
Click to expand...
Click to collapse
You are correct...That is the name of the actual image in the UPDATE.APP, but I was basing the name off of the actual partition.
Corrections, please add to original post
smokinjoe2122 said:
You are correct...That is the name of the actual image in the UPDATE.APP, but I was basing the name off of the actual partition.
Click to expand...
Click to collapse
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
crayonicle said:
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
System image can fail too...that's why I said to flash everything in TWRP...Plus, flashing the update on-top of itself will not only give you theming back, but stock recovery.
crayonicle said:
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
Is this working ? Did you try ? I'm on RR ROM and couldn't get adb recognize my device. This is my only hope to return to stock as of now.
Adithya Krishnakumar said:
Is this working ? Did you try ? I'm on RR ROM and couldn't get adb recognize my device. This is my only hope to return to stock as of now.
Click to expand...
Click to collapse
Yes, I tried it. It works flawlessly.
How can I get themes to work? I don't understand the original post, it makes no sense when explaining how to get themes to work properly. I do not know what to do with the link provided in the original post.
crayonicle said:
How can I get themes to work? I don't understand the original post, it makes no sense when explaining how to get themes to work properly. I do not know what to do with the link provided in the original post.
Click to expand...
Click to collapse
What part are you stuck on?
Essentially mrmazak created a flashable file that will take the 3 firmware files you download and flash them on top of your current firmware. This is helpful for doing an update or just reloading the firmware completely (Which is what you're trying to do)...
I'd follow the exact instructions that he's put out on that thread, but the 10,000 ft overview:
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
1.) Download files from link for your device
2.) Create a correctly named folder on your SD card, along with those files properly named in that folder (Ensure these files are named properly also.)
3.) Ensure you have the stock recovery on the SD card also.
4.) Copy the "xxx_Update.zip" he created onto your SD
5.) Flash the "xxx_Update.zip"...It will will flash the stock recovery, then boot into update mode and update with the 3 files you downloaded and put into that folder. This will basically "reflash" the firmware and give you back themes.
I would go step by step on his action list and follow them to a "T". I've verified it works perfectly. He also has a "Basic-Instructions" write up in the zip also.
My device build number was BND-L21C185, I bricked my device once but I managed to get it back. Since then I have strange build number which is system 8.0.0.046(063f). Does this method fix it?
This info helped me bring my phone back to life,thank you sir for the step by step instructions.
Found a way to get back to stock without all this hassle lol
So I thought this was the only way to get back to stock... turns out there is a much easier way
This method also enables themes, I checked myself.
https://forum.xda-developers.com/honor-7x/how-to/getting-to-stock-emui-super-easily-t3804722
Is it possible to flash all of the partitions from fastboot?
I have the BND-L34 and I am unsure as to what happened.
I have been running the RROS surdu_petru posted for about 3 weeks now and it was running fine.
2 days ago I grab my phone and it was booted into error mode. Now when I try to boot into twrp I get an error code for my recovery. When I try to boot into the system it throws a different error code for boot image.
I have a twrp backup stored on an sd card, and all 3 OTA's I saved back during the June update. I have the Pro-TeamMT app on my pc and have found/extracted every file for the brick method only get the same errors, 1 right after the other.
I am no noob, (although I am not a Senior Member with a giant banner either ) but I have been rooting android devices going on 8 years now, and have never completely bricked any of them.
My last 2 phones were Oneplus 1 and Oneplus 3, so I am familiar with flashing all the partitions using fastboot. But with those phones there were about 9 different individual flashes that needed to be done in a particular order.
Any help or advice would be greatly appreciated.
Code:
[COLOR="red"][CENTER][SIZE="4"]##DISCLAIMER##[/CENTER]
I am not responsible for any damage at your Device. This is all at your own risk.[/SIZE][/COLOR]
Code:
[COLOR="Blue"][SIZE="5"]This version is the first version so it's UNSTABLE[/SIZE][/COLOR]
Hi all,
I've searched for a recovery with the Oreo firmware and nobody shared any of them... So I hope it helps you.
I share this recovery relase builded with TWRP Builder app only for the G3221 line. At the moment it can not be used for flash operations in /data partition due to error in the filesystem but you have the ability for all the others partition, except /data. (For more, see the spoiler)
Note:
- For who need another model recovery, try to request with
the app, like me. It's all explained in link, scroll down and click on download the app.
https://twrpbuilder.github.io
OR
https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
Requirements:
- Rooted phone
- TWRP Builder app
- Oreo Firmware
WHAT WORKS:- Installations of /system partion scripts
- All type of bakup except /data
- All type of reset INCLUDED /data
(Ex: when you repair the /data filesystem, convert it from EXT4 to EXT2 and back to EXT4 (ATTENTION: YOU WILL LOSE ALL DATA!) , will guarantee the correct functioning of the /data partition.
Installation:
- Open the TWRP Builder app
- Sign In
- Select the RECOVERY button and download the file
- Go back, select the FLASH button and select the downloaded file
- Once it finish try to reboot in recovery :highfive:
Click to expand...
Click to collapse
Credit goes to:
- @TwrpBuilder -
for making this possible
- @kirito9 -
for developing this build
I got bored
SPLT said:
Code:
[COLOR="red"][CENTER][SIZE="4"]##DISCLAIMER##[/CENTER]
I am not responsible for any damage at your Device. This is all at your own risk.[/SIZE][/COLOR]
Code:
[COLOR="Blue"][SIZE="5"]This version is the first version so it's UNSTABLE[/SIZE][/COLOR]
Hi all,
I've searched for a recovery with the Oreo firmware and nobody shared any of them... So I hope it helps you.
I share this recovery relase builded with TWRP Builder app only for the G3221 line. At the moment it can not be used for flash operations in /data partition due to error in the filesystem but you have the ability for all the others partition, except /data. (For more, see the spoiler)
Note:
- For who need another model recovery, try to request with
the app, like me. It's all explained in link, scroll down and click on download the app.
https://twrpbuilder.github.io
OR
https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
Requirements:
- Rooted phone
- TWRP Builder app
- Oreo Firmware
WHAT WORKS:- Installations of /system partion scripts
- All type of bakup except /data
- All type of reset INCLUDED /data
(Ex: when you repair the /data filesystem, convert it from EXT4 to EXT2 and back to EXT4 (ATTENTION: YOU WILL LOSE ALL DATA!) , will guarantee the correct functioning of the /data partition.
Credit goes to:
- @TwrpBuilder -
for making this possible
- @kirito9 -
for developing this build
Click to expand...
Click to collapse
I got bored had a few beers. And FLASHED this image on g3223.
CONFIRMED WORKING AND WAS ABLE TO ONCE AGAIN BRING THIS DEVICE TO NEW HEIGHTS!!!
Can't say it'll work for others. But i was able to flash magisk flawlessly and my xa1 ultra will be running modules once again.
lonewolfbtown said:
I got bored had a few beers. And FLASHED this image on g3223.
CONFIRMED WORKING AND WAS ABLE TO ONCE AGAIN BRING THIS DEVICE TO NEW HEIGHTS!!!
Can't say it'll work for others. But i was able to flash magisk flawlessly and my xa1 ultra will be running modules once again.
Click to expand...
Click to collapse
Cool! Do you have the /data partition mounted in recovery?
PM me and I will add it to the thread. :good:
SPLT said:
Cool! Do you have the /data partition mounted in recovery?
PM me and I will add it to the thread. :good:
Click to expand...
Click to collapse
No I do not have data working
SPLT said:
Cool! Do you have the /data partition mounted in recovery?
PM me and I will add it to the thread. :good:
Click to expand...
Click to collapse
lonewolfbtown said:
No I do not have data working
Click to expand...
Click to collapse
Ok, I've already contacted and informed the developer... We just have to wait.
hey can you help me please about how to flash that twrp, I`ve been trying to flash it but I keep getting the same error the boot loader doesnt work when I try to get into recovery, pressing volume down and power button
michael990 said:
hey can you help me please about how to flash that twrp, I`ve been trying to flash it but I keep getting the same error the boot loader doesnt work when I try to get into recovery, pressing volume down and power button
Click to expand...
Click to collapse
Did you get it?
Love (how the hell can you love a machine??? - sorry, I guess I have NO imagination, maybe you can ...) this phone. BUT!! After backing up and restoring using LR TWRP a number of times, then using fastboot to flash_all the original ROM a number of times when I got into flashing problems, my cavalier approach backfired in one of these repetitive actions. Surprisingly, at least to me, I have both IMEI's listed on the status page, but a constant "unknown baseband" version. SIM setting is grayed-out, and I am only on WiFi. Flashing the original ROM (V 10.4.2.0) fixed nothing. Tried V 10.4.1.0, but I can't downgrade: luckily the phone wasn't bricked. Flashed Havoc V 2.9, hoping all partitions would be overwritten, then flashed MIUI V 10.4.2.0, but no change.
Have found no solution from Hovatek (stated flashing original ROM usually repairs the unknown baseband issue), or other sites searched from Google. Any procedure to solve this MTK issue on this phone would be most appreciated.
fastboot flash_all IS already deleting & overwriting all partitions, but I found sth interesting going on both my RN8P:
1. Sometimes both of the bluetooth MAC is gone on normal reboot, replaced by generic one 00:00:46:00:00:01 (yes, both got identical MAC).
2. One of the phone can't recognize SIM card after reboot, need another reboot to fix it.
Turned out that somewhere in upgrading to MIUI 11 Android 10 ver, it's corrupting some partitions: nvcfg, ncdata, nvram, vendor, persist, misc, cust.
Here's my fix:
1. Boot to TWRP
2. Mount those partitions then go to Advanced > Terminal, issue: mount to list the ID of the partitions
3. Unmount all partitions
4. Back to terminal, issue: e2fsck -fy /dev/block/sdcX where X is the parition ID corresponding to the list of mount above
5. It'll show that some partition is getting fixed, if done, just issue: sync
6. Reboot to MIUI, let it sit for 5 minutes, then reboot to TWRP again, redo all steps & you'll see it's still getting some errors, it's normal. Redo for 2 more times, it'll get fixed for good.
Something in the systems doesn't right, it kinda needs to readjust all the fixed partitions but in the process it also corrupting it again, therefore needing 2 - 3 more e2fsck as I said above.
Oh, if you're rooted & using AdGuard, NEVER USE Move Certificate module in the Magisk, it's the one contributing to those corruption.
Wow!! Thank you so much! I will follow each step and report what I've found.
So impressed with the detail you have given; thanks to have experts such as you willing to share.
Later ....
Crescendo Xenomorph said:
fastboot flash_all IS already deleting & overwriting all partitions, but I found sth interesting going on both my RN8P:
1. Sometimes both of the bluetooth MAC is gone on normal reboot, replaced by generic one 00:00:46:00:00:01 (yes, both got identical MAC).
2. One of the phone can't recognize SIM card after reboot, need another reboot to fix it.
Turned out that somewhere in upgrading to MIUI 11 Android 10 ver, it's corrupting some partitions: nvcfg, ncdata, nvram, vendor, persist, misc, cust.
Here's my fix:
1. Boot to TWRP
2. Mount those partitions then go to Advanced > Terminal, issue: mount to list the ID of the partitions
3. Unmount all partitions
4. Back to terminal, issue: e2fsck -fy /dev/block/sdcX where X is the parition ID corresponding to the list of mount above
5. It'll show that some partition is getting fixed, if done, just issue: sync
6. Reboot to MIUI, let it sit for 5 minutes, then reboot to TWRP again, redo all steps & you'll see it's still getting some errors, it's normal. Redo for 2 more times, it'll get fixed for good.
Something in the systems doesn't right, it kinda needs to readjust all the fixed partitions but in the process it also corrupting it again, therefore needing 2 - 3 more e2fsck as I said above.
Oh, if you're rooted & using AdGuard, NEVER USE Move Certificate module in the Magisk, it's the one contributing to those corruption.
Click to expand...
Click to collapse
Okay,
No luck here:
I have not upgraded to MIUI 11 Android 10. Still on MIUI 10 Android 9.
LR. TWRP has no mount for NVRAM or for MISC. What version of TWRP do you have?
No error messages for the other remaining sdc's - sync after each e2fsck commands. Reboot to system and still unknown baseband - repeated procedure twice, after waiting 5 and 7 minutes.
Thanks for the heads-up on the Move Certificate module and AdGuard - never installed it as it seemed to be not for Xiaomi.
ppthom said:
Okay,
No luck here:
I have not upgraded to MIUI 11 Android 10. Still on MIUI 10 Android 9.
LR. TWRP has no mount for NVRAM or for MISC. What version of TWRP do you have?
No error messages for the other remaining sdc's - sync after each e2fsck commands. Reboot to system and still unknown baseband - repeated procedure twice, after waiting 5 and 7 minutes.
Thanks for the heads-up on the Move Certificate module and AdGuard - never installed it as it seemed to be not for Xiaomi.
Click to expand...
Click to collapse
it is indeed not possible to mount an NVRAM partition, maybe the one referred to is the Mount System, you must first check the mount system to restore or backup.
for TWRP files you can adjust to your current Android Version, please check the following post.
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
Coffeemi said:
it is indeed not possible to mount an NVRAM partition, maybe the one referred to is the Mount System, you must first check the mount system to restore or backup.
for TWRP files you can adjust to your current Android Version, please check the following post.
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
Click to expand...
Click to collapse
I always find out something new. Thank you. No mount NVRAM partition. As far as mount, I thought that SYSTEM partition was always auto-mounted. Not so, it is DATA and CACHE. I have backed-up and restored with this understanding. My bad, again.
Also LR. TWRP is the 1104 version, my goto recovery, as I am always able to get out of trouble using it, except now with no baseband version. However, after using Flash_all, I have to boot into the basic system to make changes before I can restore one of my backups. In this default setup, the status lists no baseband and no IMEI. It is only on restore to my latest backup that both IMEI's are also restored, but not the baseband.
ppthom said:
I always find out something new. Thank you. No mount NVRAM partition. As far as mount, I thought that SYSTEM partition was always auto-mounted. Not so, it is DATA and CACHE. I have backed-up and restored with this understanding. My bad, again.
Also LR. TWRP is the 1104 version, my goto recovery, as I am always able to get out of trouble using it, except now with no baseband version. However, after using Flash_all, I have to boot into the basic system to make changes before I can restore one of my backups. In this default setup, the status lists no baseband and no IMEI. It is only on restore to my latest backup that both IMEI's are also restored, but not the baseband.
Click to expand...
Click to collapse
if you have properly saved a backup file of all modem and IMEI partitions, all modem data will definitely be restored, I'm sure not all of the modem partitions have been successfully backed up.
for the modem partition, sensor and IMEI, here are the names of the partitions.
- nvcfg
- nvdata
- nvram
- persist
- protect_f
- protect_s
make sure all the partition names are in your TWRP backup file.
Sent from my Redmi Note 8 Pro using XDA-Developers Legacy app
You should be able to do a DD if=/image.bin of=/dev/block/sdcX to fix if you don't have a TWRP backup
- nvcfg is sdc7
- nvdata is sdc8
- nvram is sdc18
- persist is sdc10
- protect_f is sdc11 labelled protect1
- protect_s is sdc12 labelled protect2
I assume protect_f and protect_s is protect1 and 2 but hopefully someone can confirm.
Coffeemi said:
if you have properly saved a backup file of all modem and IMEI partitions, all modem data will definitely be restored, I'm sure not all of the modem partitions have been successfully backed up.
for the modem partition, sensor and IMEI, here are the names of the partitions.
- nvcfg
- nvdata
- nvram
- persist
- protect_f
- protect_s
make sure all the partition names are in your TWRP backup file.
Sent from my Redmi Note 8 Pro using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have NOT "properly saved a backup file" with the modem partitions, and that is where my trouble lies. I am also not being reminded to set the SIM card info when booting up after flashing the stock 10.4.2.0 ROM, which is strange, because a week ago I was able to go back-and-forth between my restored backed-up files and the stock ROM. On first booting the stock ROM, I was reminded every 10 seconds that my SIM card was not correct (my card is only 3G and the default SIM setup was for LTE), interferring with setting up my WiFi for authenticating my Xiaomi account. Now, with an unknown baseband, the SIM is not recognised by the stock ROM, I can enter my WiFi account without interference; and there no entry for the baseband and nothing for the IMEI numbers.
As soon as my "not proper backup" is restored, the IMEI numbers are set correctly, but no baseband.
My goodness, I will see if anyone online can flash the stock zip file remotely and see if that corrects the problem.
Hey, thank you for paying attention to my problem, and I very much appreciate your time on this.
wang1chung said:
You should be able to do a DD if=/image.bin of=/dev/block/sdcX to fix if you don't have a TWRP backup
- nvcfg is sdc7
- nvdata is sdc8
- nvram is sdc18
- persist is sdc10
- protect_f is sdc11 labelled protect1
- protect_s is sdc12 labelled protect2
I assume protect_f and protect_s is protect1 and 2 but hopefully someone can confirm.
Click to expand...
Click to collapse
Thank you fellow Canadian :good:; I will try this as well. So great to have all these suggestions from people who know a hell of a lot more than I do. Thank you both Coffeemi and wang1chung.
ppthom said:
Okay,
No luck here:
I have not upgraded to MIUI 11 Android 10. Still on MIUI 10 Android 9.
LR. TWRP has no mount for NVRAM or for MISC. What version of TWRP do you have?
No error messages for the other remaining sdc's - sync after each e2fsck commands. Reboot to system and still unknown baseband - repeated procedure twice, after waiting 5 and 7 minutes.
Thanks for the heads-up on the Move Certificate module and AdGuard - never installed it as it seemed to be not for Xiaomi.
Click to expand...
Click to collapse
Better to use LR TWRP, it's the best for Xiaomi phone.
Sadly it's only available for Android 10 version. Better upgrade as Android 10 still way better than their 9 (too much bug).
Link to A10 LR-TWRP: https://mega.nz/file/Ad4TUTTA#_xT16vOzYK-O8qaWEHPYxfdi4wNpK5Ang9maN5iO_-U
If no error being corrected then sadly I dunno more except for hardware issue (baseband chip is broken, I saw one case in Mi Community forum). Hope not this case. :crying:
You're welcome friend. The Move Certificate module is for AdGuard actually, its to clear those network being monitored notification when you use AdGuard's HTTPS filtering.
Thank you Coffeemi, wang1chung and of course Crescendo Xenomorph. You've all paid attention to this problem, and it is very much appreciated.
Ok, ok. Not sure how I did not stumble accross this before, or, more likely, not paid attention to this procedure .
I choose to use RN8P with Miui V10.4.2.0 ROM. Gives me the most flexibility. Later Android versions restrict my wants, including using TWRP - just a personal opinion; yours may vary ...
Erased NVRAM and nvdata in this ROM, after having flashed it and rooted it, then installing X-plore File Manager apk (most other rooted file managers would work as well, if not better).
Rebooted, and the unknown baseband problem was solved, at least for me.
Then restored my latest TWRP backup of Data, Boot, System image, Vendor image and Cust image.
All seems well. No more unknown baseband, IMEI's listed as well as Bluetooth. Whew. So many good people out "there", and so many experts to thank. Thank you:good:.
ppthom said:
Ok, ok. Not sure how I did not stumble accross this before, or, more likely, not paid attention to this procedure .
I choose to use RN8P with Miui V10.4.2.0 ROM. Gives me the most flexibility. Later Android versions restrict my wants, including using TWRP - just a personal opinion; yours may vary ...
Erased NVRAM and nvdata in this ROM, after having flashed it and rooted it, then installing X-plore File Manager apk (most other rooted file managers would work as well, if not better).
Rebooted, and the unknown baseband problem was solved, at least for me.
Then restored my latest TWRP backup of Data, Boot, System image, Vendor image and Cust image.
All seems well. No more unknown baseband, IMEI's listed as well as Bluetooth. Whew. So many good people out "there", and so many experts to thank. Thank you:good:.
Click to expand...
Click to collapse
Can you provide me the steps. Because I'm having the same vesion but with IMEI Invalid. My phone accidently got update to MIUI 11 and the Baseband got ruined.!!!
Somehow Android 10 in this phone will corrupt something in nvdata if you do modification on the fly (somehow like they unable to load it properly, thus no baseband with corrupted BT MAC).
How to know if your BT MAC is corrupted? It'll default to 00:00:46:00:00:01.
BT MAC should be one step above WIFI MAC (if your WIFI MAC is AC:1C:05:AC:43:01, your BT should be AC:1C:05:AC:43:02).
Found the culprit: any Magisk version greater than 20.3 will cause this error on MTK devices.
Solution: use Magisk 20.3 stable, it's the only fix till the devs come up with the fix.