Database Develop

Fastboot files for the Razr I

This is not my work, all work done by kent.
Thanks kent.
Currently we have the Retail.eu fastboot files, more coming soon, till then happy unbricking
Download Ics fastboot files:
81.5.31006.XT890.Retail.en.EU
MD5: aa587a372ab28faef616c7ebc6c4ac53
For Brazil Visit here:
http://sbf.droid-developers.org/smi/list.php
Credits
Skrilax_CZ
Edit: Visit here to see all the available fastboot files

Warning: If your phone is not a Retail.EU model and has NOT been bootloader unlocked please do not try these.
I am unlocked and started with Retail.GB. I can flash system, boot, recovery fine. I would not suggest flashing the other parts or the whole file in RSD if you are not a Retail.EU in any case.

Yeah it's leaktime, gonna also back up those in Brazil

Skrilax_CZ said:
Yeah it's leaktime, gonna also back up those in Brazil
Click to expand...
Click to collapse
:highfive:
Love the leaks. Thanks firmware team!

Here: http://sbf.droid-developers.org/smi/list.php
Wait for it to DL.

O2 DE
CFC_signed_customer_8.7.1I-110_IFW-DE-31_O2DE.xml.zip

Hey Guys, i got a lil Question. I have to manage the RazR i Forum here in Germany. Problem is, i own just the regular RazR.
Is there any big difference by flashing the RazR i Fastboot Files, compared with the OG RazR?
BTW: Nice How to's for unlocking the Bootloader & Root. I've used them to write an German one (of course with Links to Mattlgroffs Threads )

HSD-Pilot said:
Hey Guys, i got a lil Question. I have to manage the RazR i Forum here in Germany. Problem is, i own just the regular RazR.
Is there any big difference by flashing the RazR i Fastboot Files, compared with the OG RazR?
BTW: Nice How to's for unlocking the Bootloader & Root. I've used them to write an German one (of course with Links to Mattlgroffs Threads )
Click to expand...
Click to collapse
The filesystem is different, but the basic understanding is the same. bos is the bootloader, boot is kernel, cdrom is the mounted ISO, gpt is the partition table, logo is the boot logo, ulogo is the unlocked version of bootlogo, radio, recovery, system. A few others like ifwi, dnx, and sp.img I am not too familiar with. I am posting my firmware charger (includes German O2), on here and DroidRzr.com (got a post here now).
If you want to stay safe only flash system and boot. I haven't done anything else and been find. Been on German, Brasil, EU, GB firmwares all on my GB device with GB radio fine. If you want add me on gtalk and I can help with what I can ([email protected])

Thanks for Reply, i'll add the warning in to the Fastboot Thread, after open it tomorrow. I guess i will have some Questions, so i will send you an Message via GTalk.
Meanwhile i'm lurking on Amazon and the i will be realesed in Germany tomorrow.
We'll see, maybe something new to play with this year...

mattlgroff said:
Warning: If your phone is not a Retail.EU model and has NOT been bootloader unlocked please do not try these.
I am unlocked and started with Retail.GB. I can flash system, boot, recovery fine. I would not suggest flashing the other parts or the whole file in RSD if you are not a Retail.EU in any case.
Click to expand...
Click to collapse
How can you flash files bigger then 100mb.
I can't flash the system_signed because file is too big.
So now i have a bricked phone..

arnoldl said:
How can you flash files bigger then 100mb.
I can't flash the system_signed because file is too big.
So now i have a bricked phone..
Click to expand...
Click to collapse
The new RSD Lite supports it (I believe) as well as the new fastboot binary.
Thanks to http://aosp.us for these: http://www.aosp.us/wp-content/files/fastboots.zip

mattlgroff said:
The new RSD Lite supports it (I believe) as well as the new fastboot binary.
Thanks to http://aosp.us for these: http://www.aosp.us/wp-content/files/fastboots.zip
Click to expand...
Click to collapse
YOU'RE THE BEST!!!!! that's it...
my phone is now back alive with the EN firmware....
THANKS!!

Anyone with an locked BootLoader tried to flash the Retail EU by using RSD 6.1.4?
It would be great, if someone can confirm that they're flashable like regular Fastboots on an XT910 with the newer Version of RSD.

Locked=Yes...(for me)...

therazrguy said:
...Currently we have the Retail.eu fastboot files, more coming soon, ...
Click to expand...
Click to collapse
Hi,
I have a RAZRi with system version 81.5.32002.XT890.Retail.en.EU... If you are interrested and if someone explain me how to extract it to a file, I can punlish this version...

lebobo said:
Hi,
I have a RAZRi with system version 81.5.32002.XT890.Retail.en.EU... If you are interrested and if someone explain me how to extract it to a file, I can punlish this version...
Click to expand...
Click to collapse
I will PM you the info

mattlgroff said:
I will PM you the info
Click to expand...
Click to collapse
Why is that, wouldn't the info be interessing for everyone ?

JackyJack said:
Why is that, wouldn't the info be interessing for everyone ?
Click to expand...
Click to collapse
Maybe, it's not a big secret...it's common android debugging commands. I've already posted the system backup command, and pulling the boot.img is just a dd command to copy it to the SD card.
Code:
adb shell
su
make_ext4fs -s -l 885768704 -a system /sdcard/system.img.ext4 /system
dd if-/dev/block/mmcblk0p5 of=/sdcard/boot.img

Yeah I saw it before, but where ever the questions is, we should be able to find the answer

New Updates 32
Enviado desde mi HTC Sensation XE with Beats Audio Z715e usando Tapatalk 2

No cell service in areas that should have cell service

Hi,
I have an Atrix HD with an unlocked bootloader and root access running on Bell Canada. Before getting my AHD, I was using an HTC HD7 running Deepshining Rom 7.8.
When driving around in my car with the phone connected to my handfree BT speakerphone, I would sometimes get a message that I have no cell service on my AHD. I tend to drive the same routes and this never happened with my HTC. I have this issue with all custom 4.2.2 roms I have tried. The baseband version is MB886_BP_100740.071.6561P.
Anyone else experience this issue?
Any information would be appreciated.
Thanks

audit13 said:
Hi,
I have an Atrix HD with an unlocked bootloader and root access running on Bell Canada. Before getting my AHD, I was using an HTC HD7 running Deepshining Rom 7.8.
When driving around in my car with the phone connected to my handfree BT speakerphone, I would sometimes get a message that I have no cell service on my AHD. I tend to drive the same routes and this never happened with my HTC. I have this issue with all custom 4.2.2 roms I have tried. The baseband version is MB886_BP_100740.071.6561P.
Anyone else experience this issue?
Any information would be appreciated.
Thanks
Click to expand...
Click to collapse
this is because of signal changing from 3g to lte or vice versa,, if you dont want that you can change prefrance to only lte or only hspa+ on *#*#4636#*#*

audit13 said:
Hi,
I have an Atrix HD with an unlocked bootloader and root access running on Bell Canada. Before getting my AHD, I was using an HTC HD7 running Deepshining Rom 7.8.
When driving around in my car with the phone connected to my handfree BT speakerphone, I would sometimes get a message that I have no cell service on my AHD. I tend to drive the same routes and this never happened with my HTC. I have this issue with all custom 4.2.2 roms I have tried. The baseband version is MB886_BP_100740.071.6561P.
Anyone else experience this issue?
Any information would be appreciated.
Thanks
Click to expand...
Click to collapse
Try the Mex Retail baseband -- is version QINARA_BP_100740.081.65.05p. I have great service with it (better than Stock AT&T JB actually).
//Due to my paranoia, I take different routes all the time. I just don't like the police seeing me take the same route over and over again....

Aingaran said:
this is because of signal changing from 3g to lte or vice versa,, if you dont want that you can change prefrance to only lte or only hspa+ on *#*#4636#*#*
Click to expand...
Click to collapse
Hi,
Would this be the same as changing option under mobile network or should I use your option to make it stick?
Thanks for your help.
skeevydude said:
Try the Mex Retail baseband -- is version QINARA_BP_100740.081.65.05p. I have great service with it (better than Stock AT&T JB actually).
Click to expand...
Click to collapse
Hi,
Is that the rom under your stock AHD rom thread? If it is, can I just flash it using cwm like I did with the untested Bell rom?
Edit: I should mention that I disable my data connection unless I'm checking my email or surfing the WWW.

audit13 said:
Hi,
Would this be the same as changing option under mobile network or should I use your option to make it stick?
Thanks for your help.
Hi,
Is that the rom under your stock AHD rom thread? If it is, can I just flash it using cwm like I did with the untested Bell rom?
Click to expand...
Click to collapse
ya, nearly same.... but once rebooted, it goes back to default, should change at every reboot.. and stock MR is available in that same thread and it is not CWM flashable.. you need to flash it through fastboot..

Aingaran said:
ya, nearly same.... but once rebooted, it goes back to default, should change at every reboot.. and stock MR is available in that same thread and it is not CWM flashable.. you need to flash it through fastboot..
Click to expand...
Click to collapse
Thanks. I'll try changing the preferred network using the hidden menu.

audit13 said:
Hi,
Would this be the same as changing option under mobile network or should I use your option to make it stick?
Thanks for your help.
Hi,
Is that the rom under your stock AHD rom thread? If it is, can I just flash it using cwm like I did with the untested Bell rom?
Edit: I should mention that I disable my data connection unless I'm checking my email or surfing the WWW.
Click to expand...
Click to collapse
Yes, but that rom only contains the MR system and is/was made for the stock AT&T kernel.
Download the fastboot and manually flash just the radio. No wipe required that way.

skeevydude said:
Yes, but that rom only contains the MR system and is/was made for the stock AT&T kernel.
Download the fastboot and manually flash just the radio. No wipe required that way.
Click to expand...
Click to collapse
Just downloaded the Mexico rom from Goo. Took quite a while. I'll have to do some research to figure out how to flash the radio. Thanks for your help.

audit13 said:
Just downloaded the Mexico rom from Goo. Took quite a while. I'll have to do some research to figure out how to flash the radio. Thanks for your help.
Click to expand...
Click to collapse
Extract the fastboot
Download the snapdragon fastboots (linked in fastboot guide)
Place the appropriate one in the folder with the fastboot's files
fastboot flash modem NON-HLOS.bin

skeevydude said:
Extract the fastboot
Download the snapdragon fastboots (linked in fastboot guide)
Place the appropriate one in the folder with the fastboot's files
fastboot flash modem NON-HLOS.bin
Click to expand...
Click to collapse
Okay, I have the NON-HLOS.bin file from the Mexico retail. I assume I have to do the following on my Windows machine:
1) install the adb/fastboot files to a single directory on my computer;
2) place the NON-HLOS.bin file in the adb/fastboot directory from step 1;
3) open a command prompt window as an administrator;
4) install the Motorola USB drivers and connect my booted phone with USB debugging enabled;
5) from the command line, type "adb reboot bootloader" and press the enter key to get my phone into AP Fastboot Flash mode;
6) from the command line, type "fastboot flash modem NON-HLOS.bin" and press enter; and
7) reboot the phone and check to made sure my baseband now says "QUINARA_BP_100740.081.65.05P".
If I want to flash back to the stock Bell baseband, I assume I would substitute the Mexico NON-HLOS.bin file for the Bell file.
Pardon my noobness. It's just that I don't want to screw up my phone. It's barely 3 months old.

audit13 said:
Okay, I have the NON-HLOS.bin file from the Mexico retail. I assume I have to do the following on my Windows machine:
1) install the adb/fastboot files to a single directory on my computer;
2) place the NON-HLOS.bin file in the adb/fastboot directory from step 1;
3) open a command prompt window as an administrator;
4) install the Motorola USB drivers and connect my booted phone with USB debugging enabled;
5) from the command line, type "adb reboot bootloader" and press the enter key to get my phone into AP Fastboot Flash mode;
6) from the command line, type "fastboot flash modem NON-HLOS.bin" and press enter; and
7) reboot the phone and check to made sure my baseband now says "QUINARA_BP_100740.081.65.05P".
If I want to flash back to the stock Bell baseband, I assume I would substitute the Mexico NON-HLOS.bin file for the Bell file.
Pardon my noobness. It's just that I don't want to screw up my phone. It's barely 3 months old.
Click to expand...
Click to collapse
Yes to all, but with step 6, make damn sure you're using the fastboot from the guide. Using the SDK fastboot is the cause of 99% of the fastboot questions we answer.
LoL @ 3 Months. Flashed my first android rom (2.5 years ago) within 4 hours of having my Bravo -- and I had never even used an Android Phone before that. Found XDA during the initial charge, read up on my phone, learned a bit, and flashed away. Luckily I'm a quick studier and learner. Didn't even join XDA till 6 months later. Saw some questions I could answer, joined, and answered them....now I compile roms and am learning Java. XDA is a great place if you use it properly.

skeevydude said:
Yes to all, but with step 6, make damn sure you're using the fastboot from the guide. Using the SDK fastboot is the cause of 99% of the fastboot questions we answer.
LoL @ 3 Months. Flashed my first android rom (2.5 years ago) within 4 hours of having my Bravo -- and I had never even used an Android Phone before that. Found XDA during the initial charge, read up on my phone, learned a bit, and flashed away. Luckily I'm a quick studier and learner. Didn't even join XDA till 6 months later. Saw some questions I could answer, joined, and answered them....now I compile roms and am learning Java. XDA is a great place if you use it properly.
Click to expand...
Click to collapse
Thanks for the confirmation. I just finished flashing the radio and it's all good so far. I used the fastboot files from the Myth Tools and they worked without any issues. Maybe I got lucky:fingers-crossed:
I've rooted some Samsung and HTC phones using the great guides on this forum and a helping hand from users like yourself.
Could I compile roms? I doubt it. I don't think I'm anywhere close to being that competent.

audit13 said:
Thanks for the confirmation. I just finished flashing the radio and it's all good so far. I used the fastboot files from the Myth Tools and they worked without any issues. Maybe I got lucky:fingers-crossed:
I've rooted some Samsung and HTC phones using the great guides on this forum and a helping hand from users like yourself.
Could I compile roms? I doubt it. I don't think I'm anywhere close to being that competent.
Click to expand...
Click to collapse
The files with Myth are the proper ones. I think most Myth Tools issues are from when/if whomever followed an SDK Install Guide that had whomever add the SDK fastboot to the system's $PATH. If you've never installed the SDK or only use Myth, you'll be fine.
Thanks. Remember back when rooting was as simple as installing an APK from the market? Good times back then.
You probably could compile them, its fixing it when the compile breaks that's the actual hard part (or waiting on upstream to fix it that's the really hard part ....waiting sucks )

downloaded the mexico retail from goo.im and extracted the .zip, but where is the NON-HLOS.bin file?
?

davwman said:
downloaded the mexico retail from goo.im and extracted the .zip, but where is the NON-HLOS.bin file?
?
Click to expand...
Click to collapse
Try here: http://sbf.droid-developers.org/dinara/list.php

FLashed Wrong ROM (downgraded)

Hello everyone,
I have a XT1079 and I made the mistake of flashing 1069´s ROM. Now I can´t install a custom rom and adb does not recognize my device (it is listed as 1069 with a question mark on the icon in device manager).
Any ideas for help me will be appreciated, thanks a lot.

If your phone is able to go into recovery , you just flash the stock firmware again or flash flashable zip of the stock ROM ( or may be some custom ROM (i'm not sure though)). This will kind of reset your phone and it will work again. But as you said, You have downgraded your phone, you need to check out which one to flash ...i mean whether to flash kitkat or lollipop version.

Custom ROM
andromuks said:
If your phone is able to go into recovery , you just flash the stock firmware again or flash flashable zip of the stock ROM ( or may be some custom ROM (i'm not sure though)). This will kind of reset your phone and it will work again. But as you said, You have downgraded your phone, you need to check out which one to flash ...i mean whether to flash kitkat or lollipop version.
Click to expand...
Click to collapse
Problem is that the stock rom does not come in a zip file and I receive downgrade error msg when I try to flash via mfastboot. But I want to use Cyanogenmod ROM. Thanks again.

GeekMaga said:
Hello everyone,
I have a XT1079 and I made the mistake of flashing 1069´s ROM. Now I can´t install a custom rom and adb does not recognize my device (it is listed as 1069 with a question mark on the icon in device manager).
Any ideas for help me will be appreciated, thanks a lot.
Click to expand...
Click to collapse
install motorola device manager 2.5.4 .exe for fastboot drivers for all motorola's and see if ADB recognises it then?

GeekMaga said:
Hello everyone,
I have a XT1079 and I made the mistake of flashing 1069´s ROM. Now I can´t install a custom rom and adb does not recognize my device (it is listed as 1069 with a question mark on the icon in device manager).
Any ideas for help me will be appreciated, thanks a lot.
Click to expand...
Click to collapse
If you flashed XT1069 motoboot.img then you're simply screwed as you won't be able to connect to mobile network.

One more try
LuK1337 said:
If you flashed XT1069 motoboot.img then you're simply screwed as you won't be able to connect to mobile network.
Click to expand...
Click to collapse
I sent to a technician to restore stock firmware and I will follow the tutorial here in the forum for the right model. Closing thread.

Solved for now
reefuge said:
install motorola device manager 2.5.4 .exe for fastboot drivers for all motorola's and see if ADB recognises it then?
Click to expand...
Click to collapse
Too late but thanks anyway I sent it to a local cell phone repair shop. After that I will follow the tutorial here to install rom and google apps thank you very much.

Man it´s never too late for android
I solved the first part. I was using titan files and for XT1078 the correct one is thea. Problem now is that none of the sim cards are recognized by the firmware. Any ideas guys
I used twrp (mfastboot flash recovery <file_name>. and it´s interface it is pretty friendly. Also installed google apps zips. It is amazing how much you can customize with this ROM.

GeekMaga said:
I solved the first part. I was using titan files and for XT1078 the correct one is thea. Problem now is that none of the sim cards are recognized by the firmware. Any ideas guys
Click to expand...
Click to collapse
you have a xt1079 right? stop flashing WRONG files until you get correct xt1079 firmware - please tell us what you originally had on phone and we will try to find it for you.
I cant seem to find any brazil xt1079 firmwares - yet - you have no signal due to incorrect radio/modem files - only can find xt1079 retcn files this modem / radio combo will be wrong - yours will become available but may take months to appear.....
THIS is why we backup our stock roms with TRWP to include the PDS area

[XT1789-05] Stock OREO Firmware (retbr)

Hey dudes,
since no one ever did this, I uploaded all Oreo Stock (retbr) for or beloved XT1789-05 released so far.
Here are the link:
https://www.dropbox.com/sh/emeuwiyaxpqqu56/AABKMNnrmMOwR5S0pBH2d7lWa?dl=0
The folder also contains RSD-lite for Mac and Linux users.
Enjoy.
if you are a Linux or Mac user and don't know how to use RSD, *I'll show you how to do with simple steps.
here we go:
1- Unzip the RSD-lite folder on your desktop;
2- Unzip the firmware zip and copy all files to the RSD folder on your desktop;
3- Open your terminal and go to the RSD-lite folder and connect your cellphone on USB with USB DEBUBBING ON;
4- Type this commands and hit ENTER after every line:
adb reboot bootloader
if you are on Linux;
bash rsd-flash.sh flashfile.xml
if you are on Mac:
./rsd-flash.sh flashfile.xml
press enter to start the flash from terminal
5- Watch for any errors. If no errors at the end of the script then press enter to reboot the device.
Many thanks to @Liboicl for the Linix script and @rootjunky for Mac script.

I'll keep adding the firmware on this folder as soon they pop up .

Does it flash to both slots? If not, this won't prepare the -05 model for AOSP ROMs. The T-Mobile flash all and Sprint ones flash to both slots via .sh or .bat files

Uzephi said:
Does it flash to both slots? If not, this won't prepare the -05 model for AOSP ROMs. The T-Mobile flash all and Sprint ones flash to both slots via .sh or .bat files
Click to expand...
Click to collapse
It flash both partitions, the script just compile all fastboot comands

darthxa said:
It flash both partitions, the script just compile all fastboot comands
Click to expand...
Click to collapse
So if you do "fastboot --set-active=_b" it will boot to system just fine?

Uzephi said:
So if you do "fastboot --set-active=_b" it will boot to system just fine?
Click to expand...
Click to collapse
As soon I get home I'll Test and do do sure

Uzephi said:
So if you do "fastboot --set-active=_b" it will boot to system just fine?
Click to expand...
Click to collapse
That's what I got
Perhaps it's because I have patched boot image in system B
But if that helped...

darthxa said:
That's what I got
Perhaps it's because I have patched boot image in system B
But if that helped...
Click to expand...
Click to collapse
That happened because the bootloader noticed slot B doesn't have Oreo firmware on it. I'll make a .sh and .bat for you in a couple of days for AOSP from the files in that zip. It will be firmware only, no system or OEM images as it will be for AOSP prep more than back to stock.

Uzephi said:
That happened because the bootloader noticed slot B doesn't have Oreo firmware on it. I'll make a .sh and .bat for you in a couple of days for AOSP from the files in that zip. It will be firmware only, no system or OEM images as it will be for AOSP prep more than back to stock.
Click to expand...
Click to collapse
Let me ask you, do you know if this particular model is eu version or America version? I'm trying install twrp ....

darthxa said:
Let me ask you, do you know if this particular model is eu version or America version? I'm trying install twrp ....
Click to expand...
Click to collapse
Installing twrp shouldn't matter the model. Just boot to twrp and flash the zip, it will edit your current boot image and not mess with any special properties like radio stuff that differ from model to model.

Hello. The new firmware has been released with the March patch NASH_OPXS27.109-34-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. Would you kindly be able to post the link? Thanks!!!

solocchi said:
Hello. The new firmware has been released with the March patch NASH_OPXS27.109-34-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. Would you kindly be able to post the link? Thanks!!!
Click to expand...
Click to collapse
Hi, I found it here https://plus.google.com/communities...1/stream/74c3716d-1a33-42b4-a515-63f32f4401e1, specificially in this post https://plus.google.com/111081030652026277798/posts/APCeCosyCX3 just by searching for exactly the filename you provided above with google.

Thanks for the link. I already know it but it doesn't work. I tried again and appear the message: access denied.
If you can download it and share it could be great.

solocchi said:
Thanks for the link. I already know it but it doesn't work. I tried again and appear the message: access denied.
If you can download it and share it could be great.
Click to expand...
Click to collapse
it's weird, i've got 2 pc, 1 access denied and download fine for the other

ilovemeow said:
it's weird, i've got 2 pc, 1 access denied and download fine for the other
Click to expand...
Click to collapse
I can not with any pc. If you have downloaded the firmware I would ask you kindly to post it. Thank you.

solocchi said:
I can not with any pc. If you have downloaded the firmware I would ask you kindly to post it. Thank you.
Click to expand...
Click to collapse
http://myown1gbb2.ddns.net:13955/sharing/sQf3mIAgr
password: MotoZ2ForceXT1789

ilovemeow said:
http://myown1gbb2.ddns.net:13955/sharing/sQf3mIAgr
password: MotoZ2ForceXT1789
Click to expand...
Click to collapse
Thanks!!!

darthxa said:
... for our beloved XT1789-05 ...
Click to expand...
Click to collapse
I wouldn't go as far as beloved
For me, this is actually the worst Moto phone I've ever owned (and I've owned 4 of them), specially by the price I paid for it... the phone doesn't worth not even half the price.
In fact, this is my last Moto ever, I'm done with Moto/Lenovo or any other Chinese crap for that matter.

Uzephi said:
I'll make a .sh and .bat for you in a couple of days for AOSP from the files in that zip.
Click to expand...
Click to collapse
I don't mean to push you or anything, I'm just curious if you were able to make the .bat/.sh file for this version (retbr)?

felipevsw said:
I don't mean to push you or anything, I'm just curious if you were able to make the .bat/.sh file for this version (retbr)?
Click to expand...
Click to collapse
My bat file in my thread will only work with official releases from the Motorola Firmware Team (MFT). I.E. with the official firmware and my .bat you will be able to take OTAs again. I cannot guarantee any other zips.

Updating BTV-DL09 to new, unapproved, firmware

Hi all!
First a warning: I tell you how what I done, applying this on different model is possible but require some knowledge... don't try if you are not enough experienced.
My BTV-DL09 had a C100B303 firmware (unlocked, rooted with SuperSu 2.82) and I wanted to upgrade to last version, B310, downloaded with Firmware Finder for Huawei.
But this formware is not yet approved for my device! So i searched a way to update the firmware and found HuRUpdater.
Here the step-by-step tutorial:
1) download version B310
2) rename files (required by HuRUpdater):
- update_data_full_public.zip -> update_data_public.zip
- update_full_BTV-DL09_hw_eu.zip -> update_all_hw.zip
3) download HuRUpdater, I used version 0.3 if a new is available read what's changed.
4) (optional) download custom recovery (in this case the Greatslon TWRP for EMUI 5) and rename it "recovery.img"
5) copy all files to SD, in a subfolder (don't use "dload")
6) install, if not already present, the custom recovery
7) boot to the recovery and install "HuRUpdater_0.3.zip"
8) follow on-screen instructions than reboot!
At this point the Mediapad was working BUT
A) without root
B) with a "half" lock: the bootloader says it's unlocked but refused to flash or boot a custom recovery.
Problem B: I had to re-unlock the booloader with command
fastboot oem unlock 12345678901234567980
I accepted that my data will be erased (I have a backup, you too???) and the Mediapad rebooted.
I was lucky because the data was not erased and the bootloader now was fully unlocked. I'm not sure if this works for all of you so backup your data before. (***)
Problem A: not the custom recovery is booting so I flashed Magisk 15.3 (I had this version on other devices and don't wanted to do more testing for that day). It installed correctly, rebooted and
that's all folks!
(***) Here the enlightenment: https://forum.xda-developers.com/showpost.php?p=78194270&postcount=1029 from @zxz0O0
In short: flash also the custom recovery!

I have a M3 that can only boot up to twrp. I am trying to fix this tablet, since the previous owner accidentally erased the system partition, and it will not load. I did a search using the firmware finder, but wasn't sure I did it right, alot of versions came up. I do not know what software version was on it, before it got messed up. All I know is that it was bought less than two months ago. I was hoping someone could post a direct link to the firmware that I could use to get this tablet up and running again. the original owner lives in the US, as do I. Any help will be greatly appreciated. Thanks in advance

thew-tab said:
I have a M3 that can only boot up to twrp. I am trying to fix this tablet, since the previous owner accidentally erased the system partition, and it will not load. I did a search using the firmware finder, but wasn't sure I did it right, alot of versions came up. I do not know what software version was on it, before it got messed up. All I know is that it was bought less than two months ago. I was hoping someone could post a direct link to the firmware that I could use to get this tablet up and running again. the original owner lives in the US, as do I. Any help will be greatly appreciated. Thanks in advance
Click to expand...
Click to collapse
First you need to know the exact model. One method can be this:
0) insert an SD card
1) boot the TWRP
2) open the terminal
3) execute the command:
Code:
dd if=/dev/block/bootdevice/by-name/oeminfo of=/external_sd/oeminfo.img
this will copy the OEMINFO partition to the SD card.
4) open the oeminfo.img file with a hex editor and search for "BTV", do not stop to the first occurrence: there are some and you will find the exact firmware code that was installed.
5) search a FULL firmware with FW finder than flash it!
Nicola

nicolap8 said:
First you need to know the exact model. One method can be this:
0) insert an SD card
1) boot the TWRP
2) open the terminal
3) execute the command:
Code:
dd if=/dev/block/bootdevice/by-name/oeminfo of=/external_sd/oeminfo.img
this will copy the OEMINFO partition to the SD card.
4) open the oeminfo.img file with a hex editor and search for "BTV", do not stop to the first occurrence: there are some and you will find the exact firmware code that was installed.
5) search a FULL firmware with FW finder than flash it!
Nicola
Click to expand...
Click to collapse
Hello. I messed up my M3 trying to update and now Bluetooth does not work.
My firmware shows in Settings as "testkeys", so I don't really now what firmware is, probably B302 since security patch is from November 2017.
I am trying to flash full firmware again and do a full wipe. I tried to do it via TWRP and eRecovery too, but both methods fail.
I also tried the method the OP mentioned with no luck either (maybe because mine is the WiFi-only European version).
What should I do? How do I go back to stock? I don't care if I lose my data or if I have to relock bootloader again, I just want my M3 to work properly again!

sergio_sant said:
Hello. I messed up my M3 trying to update
Click to expand...
Click to collapse
Exact model?
Exact firmware that you have?

nicolap8 said:
Exact model?
Exact firmware that you have?
Click to expand...
Click to collapse
Model is BTV-W09C100B006 according to oeminfo.img, so I guess firmware must be B006?
In Settings it shows up like the screenshot attached:

sergio_sant said:
Model is BTV-W09C100B006 according to oeminfo.img, so I guess firmware must be B006?
In Settings it shows up like the screenshot attached:
Click to expand...
Click to collapse
Ahi, ahi... you are unable to discriminate what is the device model (BTV-W09) from the firmware version (BTV-W09C100B006). So you are not enough experienced nor skilled... Search someone that can help you offline!

nicolap8 said:
Ahi, ahi... you are unable to discriminate what is the device model (BTV-W09) from the firmware version (BTV-W09C100B006). So you are not enough experienced nor skilled... Search someone that can help you offline!
Click to expand...
Click to collapse
I may be not enough experienced nor skilled but I've been unlocking, rooting and changing roms to my phones since Android 2.1 era, that was many years ago as you know.
I know that the model is BTV-W09, I just said that OEMINFO says BTV-W09C100B006 when searching "btv" with an hex-editor following YOUR instructions from your earlier post.
Anyway, thanks for nothing, I finally found a solution by myself writing the required images one by one trough ADB.
Have a nice day.

I had to have messed up something quite well, I ran the updater, everything seemed to go fine, but when I rebooted, it wont go off the Huawei MediaPad android screen, and I can not get it back into TWRP , or get it to do anything else, any help would be greatly appreciated.
nicolap8 said:
First you need to know the exact model. One method can be this:
0) insert an SD card
1) boot the TWRP
2) open the terminal
3) execute the command:
Code:
dd if=/dev/block/bootdevice/by-name/oeminfo of=/external_sd/oeminfo.img
this will copy the OEMINFO partition to the SD card.
4) open the oeminfo.img file with a hex editor and search for "BTV", do not stop to the first occurrence: there are some and you will find the exact firmware code that was installed.
5) search a FULL firmware with FW finder than flash it!
Nicola
Click to expand...
Click to collapse

thew-tab said:
I had to have messed up something quite well, I ran the updater, everything seemed to go fine, but when I rebooted, it wont go off the Huawei MediaPad android screen,
Click to expand...
Click to collapse
Explain better, which screen?
and I can not get it back into TWRP , or get it to do anything else, any help would be greatly appreciated.
Click to expand...
Click to collapse
Reread first post.

It is the initial boot screen
nicolap8 said:
Explain better, which screen?
Reread first post.
Click to expand...
Click to collapse

Model?
Firmware previously on tablet?
Firmware that you installed?
Which files you used?
The update procedure was successfully or there was some message?

Model number is BTV-W09
Do not know the original firmware, but I apparently read the model number wrong when I looked it up. I used BTV-DL09. TWRP said install was a success ( I used the HuRUupdater thru TWRP) The files used was the full OTA , the update_full_BTV-DL09_dialcu_cn.zip, as well as the update_data_full_public.zip. I changed the file name to the names that were needed to run HuRUpdater. So my question is does anyone know how to fix my mistake?
I was able to get it into fastboot mode, but it said the phone was locked, and was not picked up by my computer.
nicolap8 said:
Model?
Firmware previously on tablet?
Firmware that you installed?
Which files you used?
The update procedure was successfully or there was some message?
Click to expand...
Click to collapse

thew-tab said:
Model number is BTV-W09
I used BTV-DL09. TWRP said install was a success
Click to expand...
Click to collapse
NEVER install the software for one model on a different hardware. NEVER!
What TWRP says it's not important: it only wrote some files on a disk but it's not of interest what is inside these files.
You have to flash an appropriate firmware, no other options.

how can I flash the the firmware, if I no longer have TWRP, or when I can get into flashboot mode, the computer does not recognize the tablet? . Here is a probably stupid question: do I look for BTV-W09, which is the model of MY tablet?
nicolap8 said:
NEVER install the software for one model on a different hardware. NEVER!
What TWRP says it's not important: it only wrote some files on a disk but it's not of interest what is inside these files.
You have to flash an appropriate firmware, no other options.
Click to expand...
Click to collapse

thew-tab said:
how can I flash the the firmware, if I no longer have TWRP, or when I can get into flashboot mode. Here is a probably stupid question: do I look for BTV-W09, which is the model of MY tablet?
Click to expand...
Click to collapse
You have to unpack the firmware and flash the partition images with flashboot.
Search the forum for "Huawei Update Extractor".

which of these are the partition images? Second stupid question, I tried to get in to fastboot, but the computer would not recognize the tablet
nicolap8 said:
You have to unpack the firmware and flash the partition images with flashboot.
Search the forum for "Huawei Update Extractor".
Click to expand...
Click to collapse

thew-tab said:
which of these are the partition images? Second stupid question, I tried to get in to fastboot, but the computer would not recognize the tablet
Click to expand...
Click to collapse
All of this are partition images!
The problem is that you have to write all relevant partitions that was written from bad firmware!
Often boot.img is enough to have TWRP working.

What about if I can't get the computer to recognize the tablet in fastboot mode?
nicolap8 said:
All of this are partition images!
The problem is that you have to write all relevant partitions that was written from bad firmware!
Often boot.img is enough to have TWRP working.
Click to expand...
Click to collapse

This is the screen I see when I am in flashboot mode
thew-tab said:
What about if I can't get the computer to recognize the tablet in fastboot mode?
Click to expand...
Click to collapse