Database Info

[Help] Can't flash system images to xt1031 Republic Wireless

So, last week I received the update to 4.4.4 on my Republic Wireless xt1031 (locked bootloader), then quickly realized that I preferred 4.4.2. After this, I downloaded the official republic wireless 4.4.2 firmware and attempted to flash it with fastboot, which didnt do anything but wipe my data. I then retried with mfastboot, which softbricked my phone. Whenever I try to flash any of the many stock firmwares I have found (tried Republic Wireless, Boost and a couple other firmwares, including a couple 4.4.4 firmwares), it seems that everything has been able to flash over and is working other than the system image files (system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 for the stock republic wireless firmwares). Whenever I try to flash any of the 3 over, I get an error on the phone:
hab check failed for system
Invalid PIV signed system image
and in my command prompt:
...\falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-key
s-cid6.xml>mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (256840 KB)...
OKAY [ 8.056s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.464s
I've heard this can be an issue with a locked bootloader, but I've also read that people can flash stock roms with a locked bootloader as long as the firmware is specifically for your phone. Does anyone have any advice on this issue? I'm just about at my wit's end here. I have tried at least 6 different firmware, I've intentionally hardbricked it by destroying the bootloader, then reflashed it with blankflash and Motoflasher on two separate tries and still no luck. Currently, it goes through the boot process but just boots to a black screen. Any help would be greatly appreciated.

I had a nightmare with this problem, I think it is an issue with your partitions, do you have an unlocked boot loader? If so try installing twrp recovery and check the sizes of your partitions especially /system partition and post results, I never fixed the issue I eventually got it replaced by the store I bought the phone from.
PS unlocking boot loader will void your warranty so if possible try and get the store to replace device.
Sent from my XT1039 using XDA Free mobile app

jasond567 said:
I had a nightmare with this problem, I think it is an issue with your partitions, do you have an unlocked boot loader? If so try installing twrp recovery and check the sizes of your partitions especially /system partition and post results, I never fixed the issue I eventually got it replaced by the store I bought the phone from.
PS unlocking boot loader will void your warranty so if possible try and get the store to replace device.
Sent from my XT1039 using XDA Free mobile app
Click to expand...
Click to collapse
My bootloader is not unlocked and Republic Wireless does not allow the bootloader to be unlocked. One of the reasons I was trying to downgrade was because I was going to use sunshine to unlock the bootloader, but it doesn't work on 4.4.4. I got the gpt.bin from the official update for 4.4.4 on Republic Wireless that someone had posted here on xda, as it was the noly one that would flash successfully that I have found. According to the 4.4.4 debricking guide on here, you can flash the gpt.bin and motoboot.img from a 4.4.4 firmware, then after that flash the 4.4.2 files from the stock firmware of your choice.

Ahhh I see that's The same problem I had I followed most online suggestions from XDA and others and nothing worked for me so I got a replacement phone, is that possible for you to do, fingers crossed that if you do it will come with 4.4.2
Sent from my XT1039 using XDA Free mobile app

I am getting a replacement phone sent, hoping for 4.4.2!!!

Great news, I have my fingers crossed for you
Sent from my XT1039 using XDA Free mobile app

wulfep said:
I am getting a replacement phone sent, hoping for 4.4.2!!!
Click to expand...
Click to collapse
Did you get it unlocked?

wulfep, I am exactly in your situation. Were you able to find a workaround that allows you to flash the Republic Wireless Moto G 1stgen XT1031 phone with an alternate firmware, of the same Android Lollipop version but for other Spring-based MVNOs (i.e. Boost, US Cellular, Verizon etc)? And considering that the phone has the damn Motorola bootloader locked !?
Thanks.

Rooting B324 on TL10?

Hello dear forum users.
I am new to Huawei but not to Android, having had (and rooted) devices since Eclair.
Yesterday, (Oct. 1st) I received my TL10 (European version). Looking through these forums I was excited to see that Lollipop had just been made officially available, so before doing anything else I upgraded. As I was on B125SP02 I had to first install B130, then B324.
Now, here's the thing. The rooting guides for Lollipop on these forums are for old stock ROMs and I don't want to risk bricking my new baby. I tried Kingroot, but it failed, so does anyone know if one of the rooting methods here will root B324?
Thanks in advance.

Install twrp recovery ..
Sent from my GT-P7320 using Tapatalk

Got it to work
paulopais said:
Install twrp recovery ..
Sent from my GT-P7320 using Tapatalk
Click to expand...
Click to collapse
Thanks.
I had to unlock first, which involved various running back and forth to find the unlock page on the HUAWEI site, then finding SN, IMEI and product ID. But I got there in the end.
:cyclops:

nope
afzal_b said:
Thanks.
I had to unlock first, which involved various running back and forth to find the unlock page on the HUAWEI site, then finding SN, IMEI and product ID. But I got there in the end.
:cyclops:
Click to expand...
Click to collapse
Well, I spoke too soon. TWRP detects that the phone isn't rooted and proposes swipe to root. I did it and there is a small screen that flashed too fast to read, then the phone reboots, but unfortunately with out being rooted.

afzal_b said:
Well, I spoke too soon. TWRP detects that the phone isn't rooted and proposes swipe to root. I did it and there is a small screen that flashed too fast to read, then the phone reboots, but unfortunately with out being rooted.
Click to expand...
Click to collapse
you have twrp installed ? if so, download https://download.chainfire.eu/supersu and install zip over twrp and its done

how did you unlock bootloader? the online tool need huawei id to register with me phone number and my country is not listed.

By email
Sent from my GT-P7320 using Tapatalk

Thanks again
Thanks - worked

You don't have to login with phone number
apopet26 said:
how did you unlock bootloader? the online tool need huawei id to register with me phone number and my country is not listed.
Click to expand...
Click to collapse
You can also login using with a Facebook login, which is how I did it.

afzal_b said:
You can also login using with a Facebook login, which is how I did it.
Click to expand...
Click to collapse
Yes I discovered that too after hours of struggling. Now I'm rooted and flashed back stock recovery. First time in these things and I feel proud I didn't brick anything [emoji13] After days of reading everything looks super clear I can root anything now [emoji41]
Still waiting for working xposed version though...
Send from Mate 7 using tapatalk

I got the Bootloader Unlock code and I unlocked my Mate 7 using the command "Fastboot oem unlock <code>" and it showed "done". I repeated the command and it showed "remote: already user unlocked", which convinces me that the bootloader is finally unlocked.
However, when I tried to flash TWRP recovery using "fastboot flash recovery twrp_2.8.7.0_mate7_5.1.img", I still get the same error "FAILED (remote: image verification error)". I have checked the XDA pages and the TWRP version seems to be right, as I used the link (https://basketbuild.com/devs/asyan4ik/hwmt7_l09) given on this post only.
Sequence as follows:
Fastboot Flash Recovery twrp_2.8.7.0_mate7_5.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (12644 KB)...
OKAY [ 1.384s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.404s
Is there a separate TWRP version for MT7-TL10 version? If yes, can someone provide the link, please?
This is very frustrating because it's a great phone and not being able to root is very limiting!

Xposed runs but not all modules as the Huawei theming messes with it.
As for TWRP, I don't like it and only use CWM which is what I have in my Mate7.

I tried various ways including moving back to KitKat. That landed me on a bricked device.
I then went to the website of Huawei to download the rescue package. After lot of struggle, I could get the phone to boot.
The Problem: I have been thrown off to a Chinese KitKat ROM (See attached) and no matter what I do, I am unable to flash an official International Channel ROM. The flash fails every time.
I am looking for a way to move back to either KitKat 4.4.2 or 5.1.1 B324 version of Android 5.1.1 (MT7 TL10 Model). If there is no root for 5.1.1, I would prefer to stick to the latest KitKat ROM with root.
Help.

Back to Stock Lollipop with the help of @acbka
Now need to root it with a locked bootloader. No way to unlock bootloader - even though 'Phone Unlocked' is shown on bootloader screen, yet I can't flash custom recovery through Fastboot.

[ZIP]The Newest Firmware&Modem From MIUI 9 China Beta

This is a newest MIUI 9 China Beta "s TZ &Modem
Baseband:BO.2.6.c1.2-0818_1948_87b78d2
Link:https://yadi.sk/d/wdmLsruk3MSQJr
Flashable ZIP File
Please Use TWRP

more info about updates?
is it safe, nothing to do with root/bootloader?
EDIT: DO NOT flash this on official Lineage with Lollipop bootloader, you will end up bootlooping on start, unable to get even into recovery after restart, only possible to get into fastboot which is also pretty useless, since your bootloader is locked
any idea how to recover back without going through flashing all the ROM and everything? is it possible to flash just firmware through fastboot?
EDIT 2: wanted to flash at least recovery in case it was overwritten, but I am getting
Code:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (40704 KB)...
OKAY [ 1.343s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.362s

PeterMarkoff said:
more info about updates?
is it safe, nothing to do with root/bootloader?
EDIT: do not flash this on official Lineage, you will end up bootlooping on start, unable to get even into recovery after restart, only possible to get into fastboot
any idea how to recover back without going through flashing all the ROM and everything? is it possible to flash just firmware through fastboot?
EDIT 2: wanted to flash at least recovery in case it was overwritten, but I am getting
Click to expand...
Click to collapse
kindly type, fastboot oem device-info on fastboot mode with phone pluged in,hope it didnt lock your bootloader.

yes, that piece of **** locked my lollipop bootloader, had to flash fastboot miui rom to unlock it and lost my data

PeterMarkoff said:
yes, that piece of **** locked my lollipop bootloader, had to flash fastboot miui rom to unlock it and lost my data
Click to expand...
Click to collapse
Have you unlocked your phone officially?
Because i flash this too and had no problem at all.
?

unofficially, but that never caused problems with previous updates, I guess this firmware us somehow compatible only with Nougat bootloader and locks lollipop bootloader

PeterMarkoff said:
unofficially, but that never caused problems with previous updates, I guess this firmware us somehow compatible only with Nougat bootloader and locks lollipop bootloader
Click to expand...
Click to collapse
YES,This is a Nougat Bootloader,you must unlock bootloader in official tools after you install this file in twrp

Put on a BIG ****ing warning about it being incompatible with lollipop bootloader..
And I was like "huh, my phone very smooth today, maybe I'll do a backup and try that new firmware out, shouldn't be a big deal, I've done it before np" — now it's ****ed....
(Yes I unlock the bootloader, but if I go back to marchmellow it's constant restart+bootloop.

buktore said:
Put on a BIG ****ing warning about it being incompatible with lollipop bootloader..
And I was like "huh, my phone very smooth today, maybe I'll do a backup and try that new firmware out, shouldn't be a big deal, I've done it before np" — now it's ****ed....
(Yes I unlock the bootloader, but if I go back to marchmellow it's constant restart+bootloop.
Click to expand...
Click to collapse
****ing ask before do something if you're not so sure about it.

Has anyone noticed any improvement with the new radio?

Hello. Has anyone got a link to the latest firmware available for a MI4C. I'm not after the official ROM, just firmware workable with ROMs. I think the last update I done was through andropax link https://androidfilehost.com/?w=files&flid=155424 is there a way I can also find out which firmware I have installed I forgot.
Is this the latest > https://androidfilehost.com/?fid=890278863836288705
fw_libra_miui_MI4c_V9.5.2.0.NXKCNFA_81f363e363_7.0
& will it run dev ROMs?

Locking Bootloader after OFFICIAL UNLOCK [ZE552KL]

This is not a method to relock Bootloader
I see many threads opened on the same topic and closed!
I hope those threads fixed things for you guys.
My situation is Different!
This is not a duplicate Thread.
I just unlocked bootloader on my Zenfone 3 [ZE552KL 4GB 5.5' Model]
After flashing TWRP and using ROMs based on 9.0, I found that we cannot use
UPI [Payment Interface in India (GooglePay)] in the device!
I tried many methods to flash the stock ROM and lock the Boot loader again, But I cant lock it anyway!
I found a thread by @Saktis_Impreza on this topic but I get:
adb>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.014s
I would like to share an idea which helped me Regain Warranty after rooting
and flashing over several times on the device ZUK Z2 Plus.
I'm not sure if this applies to ASUS devices.
In Z2Plus we can make the device tampered flag to false by flashing an
older Chinese Firmware on the phone using QPST Flash Tool.
Afterwards we can flash the latest firmware to get back to stock with locked Bootloader.
I know I wont get OTA since I unlocked using the OFFICIAL Method.
I just need to Relock the Bootloader.
I Hope someone would Help.
Thank You
:laugh::laugh::laugh:

rameeskr said:
This is not a method to relock Bootloader
I see many threads opened on the same topic and closed!
I hope those threads fixed things for you guys.
My situation is Different!
This is not a duplicate Thread.
I just unlocked bootloader on my Zenfone 3 [ZE552KL 4GB 5.5' Model]
After flashing TWRP and using ROMs based on 9.0, I found that we cannot use
UPI [Payment Interface in India (GooglePay)] in the device!
I tried many methods to flash the stock ROM and lock the Boot loader again, But I cant lock it anyway!
I found a thread by @Saktis_Impreza on this topic but I get:
adb>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.014s
I would like to share an idea which helped me Regain Warranty after rooting
and flashing over several times on the device ZUK Z2 Plus.
I'm not sure if this applies to ASUS devices.
In Z2Plus we can make the device tampered flag to false by flashing an
older Chinese Firmware on the phone using QPST Flash Tool.
Afterwards we can flash the latest firmware to get back to stock with locked Bootloader.
I know I wont get OTA since I unlocked using the OFFICIAL Method.
I just need to Relock the Bootloader.
I Hope someone would Help.
Thank You
:laugh::laugh::laugh:
Click to expand...
Click to collapse
Hello anyone pls help

Actually you can relock bootloader by reflashing factory raw, typing in cmd "fastboot oem unlock" and then, with bl locked, reflashing the latest oreo raw.
My tool does it automatically.

Giovix92 said:
Actually you can relock bootloader by reflashing factory raw, typing in cmd "fastboot oem unlock" and then, with bl locked, reflashing the latest oreo raw.
My tool does it automatically.
Click to expand...
Click to collapse
Thanks for your reply
I found 2 RAW images available in the internet.
I tried flashing both.
But I get the same result.
Anyway I'll try again and update.
Can you pls guide me to your tool/method.

rameeskr said:
Thanks for your reply
I found 2 RAW images available in the internet.
I tried flashing both.
But I get the same result.
Anyway I'll try again and update.
Can you pls guide me to your tool/method.
Click to expand...
Click to collapse
Here you are.
https://forum.xda-developers.com/zenfone-3/development/auto-tool-ze5xxklmodder-t3861558

rameeskr said:
This is not a method to relock Bootloader
I see many threads opened on the same topic and closed!
I hope those threads fixed things for you guys.
My situation is Different!
This is not a duplicate Thread.
I just unlocked bootloader on my Zenfone 3 [ZE552KL 4GB 5.5' Model]
After flashing TWRP and using ROMs based on 9.0, I found that we cannot use
UPI [Payment Interface in India (GooglePay)] in the device!
I tried many methods to flash the stock ROM and lock the Boot loader again, But I cant lock it anyway!
I found a thread by @Saktis_Impreza on this topic but I get:
adb>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.014s
I would like to share an idea which helped me Regain Warranty after rooting
and flashing over several times on the device ZUK Z2 Plus.
I'm not sure if this applies to ASUS devices.
In Z2Plus we can make the device tampered flag to false by flashing an
older Chinese Firmware on the phone using QPST Flash Tool.
Afterwards we can flash the latest firmware to get back to stock with locked Bootloader.
I know I wont get OTA since I unlocked using the OFFICIAL Method.
I just need to Relock the Bootloader.
I Hope someone would Help.
Thank You
:laugh::laugh::laugh:
Click to expand...
Click to collapse
Found a method to do it Finally
Pls check this thread.
https://forum.xda-developers.com/zenfone-3/development/auto-tool-ze5xxklmodder-t3861558/page4
:laugh:

Please help me to unbrick my phone !!!

Hello guys,
Last week i received my Redmi Note 7 Pro with india global rom inside with bootloader unlocked.
I tried to install TWRP and root but on every reboot it disappeared... So i decided to relock my bootloader , with fastboot oem lock, in order to make a clean unlock after that ... What a bad idea, my phone is now in boot loop in recovery mode with "this miui version can't be installed on this device" in Mi recovery.
ADB is working when i select Miassistant in Mirecovery , i can launch fastboot mode but it's impossible to flash anything beaucause my bootloader is now locked.
So i tried Mi Flash Unlock Tools to unlock my bootloader but it ask to me to change some parameters in MIUI ... Too bad my phone doesn't boot to MIUI !
So i tried the hard way with MIFlash with rom stock in EDL mode ... Too bad my MIUI account is not allowed to make it on my phone !!!
So i tried the hard way n°2 with QPST/QFIL in EDL mode with elf , xml files contained in rom stock (i tried india and china rom stock) ... To bad QFIL is crashing after "Wait for 3 seconds"...
Any ideas guys on how i can do to unbrick my phone ???
Many thanks to you.

Ok so you should have never locked the bootloader again as there were far better ways to do a clean install
Now since the bootloader is locked most system level changes aren't possible and in order for you to use the EDL method you need an authorised account (which isn't easy to get), Most Authorised Mi Service centres have one, try to visit one.
Most probably the last method you suggested doesnt work cos of the locked bootloader too... :-\

If anyone on 10.3.9 & facing bugs & want to downgrade then unlock bootloader & then download minimal adb toolkit extract it & copy the extracted fastboot rom files into minimal adb folder & then put your phone into fastboot mode & then run clear all & install.bat inside the extracted folder & wait for it to finish & you will be able to downgrade because you wont be able to downgrade with mi flash, its a tested process by me as i bricked my bootloader unlocked phone which was only going to fastboot mode, i recovered by this processprocess, but i am not sure if it will work with locked bootloader or not please check & confirm

Hello guys,
I managed to unbrick my phone by contacting Niksalsa who flashed my phone with CHINA ROM STOCK (GLOBAL DOESN'T WORK) and his xiaomi user account.
https://forum.xda-developers.com/member.php?u=5189577
unbrick.ru
Whatsapp: +79319796422
Thks

navi_58861170 said:
If anyone on 10.3.9 & facing bugs & want to downgrade then unlock bootloader & then download minimal adb toolkit extract it & copy the extracted fastboot rom files into minimal adb folder & then put your phone into fastboot mode & then run clear all & install.bat inside the extracted folder & wait for it to finish & you will be able to downgrade because you wont be able to downgrade with mi flash, its a tested process by me as i bricked my bootloader unlocked phone which was only going to fastboot mode, i recovered by this processprocess, but i am not sure if it will work with locked bootloader or not please check & confirm
Click to expand...
Click to collapse
It won't work with a locked bootloader and flashing an older update without clearing the current MIUI will enable anti rollback protection which will brick your device and the only way to unlock it would be to use an authorised account available at service centres.

I also have this problem. Xiaomi is making a mistake by limiting edl to some accounts.
Sent from my MI 6 using Tapatalk
---------- Post added at 05:52 PM ---------- Previous post was at 05:51 PM ----------
hyperj said:
Hello guys,
I managed to unbrick my phone by contacting Niksalsa who flashed my phone with CHINA ROM STOCK (GLOBAL DOESN'T WORK) and his xiaomi user account.
https://forum.xda-developers.com/member.php?u=5189577
unbrick.ru
Whatsapp: +79319796422
Thks
Click to expand...
Click to collapse
How much did you pay?
Sent from my MI 6 using Tapatalk

Naveenthemi said:
It won't work with a locked bootloader and flashing an older update without clearing the current MIUI will enable anti rollback protection which will brick your device and the only way to unlock it would be to use an authorised account available at service centres.
Click to expand...
Click to collapse
I was on 10.3.9 & i downgraded to 10.3.7 & for locked bootloader i mentioned it that check if it works & note 7pro having arb1

navi_58861170 said:
I was on 10.3.9 & i downgraded to 10.3.7 & for locked bootloader i mentioned it that check if it works & note 7pro having arb1
Click to expand...
Click to collapse
How did u downgrade having a locked bootloader and without enabling anti rollback protection...

navi_58861170 said:
I was on 10.3.9 & i downgraded to 10.3.7 & for locked bootloader i mentioned it that check if it works & note 7pro having arb1
Click to expand...
Click to collapse
Would you explain more?
Sent from my MI 6 using Tapatalk

newtonc said:
Would you explain more?
Sent from my MI 6 using Tapatalk
Click to expand...
Click to collapse
Please check with your phone note 7pro is having arb1 whereas if arb4 is there then only you cant downgrade like note 5pro, i downgraded from 10.3.9 to 10.3.7 only by unlocking bootloader by the given process, but mi flash is not working its gives error everytime

navi_58861170 said:
Please check with your phone note 7pro is having arb1 whereas if arb4 is there then only you cant downgrade like note 5pro, i downgraded from 10.3.9 to 10.3.7 only by unlocking bootloader by the given process, but mi flash is not working its gives error everytime
Click to expand...
Click to collapse
My note7pro is also running arb1 , but I'm not managing to follow your steps, there ir no clear all bat, only flash_all.bat When I run flash_all.bat, the output is only the contents.
How exactly did you run?

Anyway, i've tried to manually run the commands, and I get the output:
FAILED (remote: Flashing is not allowed in Lock State)

10.3.5.0 rom recovery and boot img file flash via fastboot and then try to unlock bootloader via internet the flash rom