Related
Hi there,
recently, I tried updating my phone to B609, following a certain website's guide.
and upon finishing it, it showed the following attachment.
I have tried following almost all I can to revert it, but sadly, it does not work. and, it was a very stupid decision of me to try and update it, full-knowingly that I have a rather obsolete knowledge regarding this.
Can someone please help me, I am really sorry to have bothered the visitors of this forum, and if my thread is not in it's place, please guide me to find a proper place to help me with my phone.
Thank you
piring said:
Hi there,
recently, I tried updating my phone to B609, following a certain website's guide.
and upon finishing it, it showed the following attachment.
I have tried following almost all I can to revert it, but sadly, it does not work. and, it was a very stupid decision of me to try and update it, full-knowingly that I have a rather obsolete knowledge regarding this.
Can someone please help me, I am really sorry to have bothered the visitors of this forum, and if my thread is not in it's place, please guide me to find a proper place to help me with my phone.
Thank you
Click to expand...
Click to collapse
Please wait confirmation from more experienced users than me but what I would have done if I were you:
1 - Try to unlock the bootloader. For that there are tutorials here in XDA: http://forum.xda-developers.com/ascend-p7/general/guide-unlock-bootloader-p7-l10-oem-t3062851
2 - With unlocked bootloader you should be able to flash a new rom!
Hope it helps!
antoniovazquezblanco said:
Please wait confirmation from more experienced users than me but what I would have done if I were you:
1 - Try to unlock the bootloader. For that there are tutorials here in XDA: http://forum.xda-developers.com/ascend-p7/general/guide-unlock-bootloader-p7-l10-oem-t3062851
2 - With unlocked bootloader you should be able to flash a new rom!
Hope it helps!
Click to expand...
Click to collapse
Thanks for the reply friend. I really appreciate it.
Regarding the unlock bootloader, following the tutorial that you have greatly linked to, it says in one of the step it to select a device. But, I did not see any mention of Ascend P7, or for that matter, I'm not aware of another given name for Ascend P7, so, which one should I choose or any selected device would be fine?
Thank you again for taking time to help me. Much appreciated.
antoniovazquezblanco said:
Please wait confirmation from more experienced users than me but what I would have done if I were you:
1 - Try to unlock the bootloader. For that there are tutorials here in XDA: http://forum.xda-developers.com/ascend-p7/general/guide-unlock-bootloader-p7-l10-oem-t3062851
2 - With unlocked bootloader you should be able to flash a new rom!
Hope it helps!
Click to expand...
Click to collapse
Also, because my phone is stuck in bootloader and can't even reboot to get past the Huawei Ascend screen, how do I get the product ID for my phone? Thank you
try with a usb jig i will try with that
Joseluisska said:
try with a usb jig i will try with that
Click to expand...
Click to collapse
Thanks for the suggestion. But apparently, I believe this is a level beyond my scarce knowledge of electronics.
But I truly appreciate the time you took to reply and suggest ways to help me. Thanks friend.
piring said:
Thanks for the reply friend. I really appreciate it.
Regarding the unlock bootloader, following the tutorial that you have greatly linked to, it says in one of the step it to select a device. But, I did not see any mention of Ascend P7, or for that matter, I'm not aware of another given name for Ascend P7, so, which one should I choose or any selected device would be fine?
Thank you again for taking time to help me. Much appreciated.
Click to expand...
Click to collapse
As it is said in the tutorial you should modify the values of the list in order to include our phone model (step 3 and following...).
Also, because my phone is stuck in bootloader and can't even reboot to get past the Huawei Ascend screen, how do I get the product ID for my phone? Thank you
Click to expand...
Click to collapse
I didn't think of that... I'm sure part of that info is available in the phone case but can't ensure that everything is there...
By the way I've never tried a JIG so any feedback on it would be nice!
i have the some problem... how i had resolved?
have u found a flashabe zip stock rom? or other way?
piring said:
Hi there,
recently, I tried updating my phone to B609, following a certain website's guide.
and upon finishing it, it showed the following attachment.
I have tried following almost all I can to revert it, but sadly, it does not work. and, it was a very stupid decision of me to try and update it, full-knowingly that I have a rather obsolete knowledge regarding this.
Can someone please help me, I am really sorry to have bothered the visitors of this forum, and if my thread is not in it's place, please guide me to find a proper place to help me with my phone.
Thank you
Click to expand...
Click to collapse
did you manage to solved your problem in your phone?if yes please help me,i got same tia
What is your exact problem? Unlocking the bootloader or flashing a new rom?
Hey bro while flashing lollipop ROM emui 3.1 in my huawei p7 it got stuck in boot loader , so I thought to revert it back to the stock ROM and I backed up my stock ROM through twrp but when I restored it It again locked my boot loader plus its stuck in boot screen... What do I do.... How am I supposed to unlock my boot loader without knowing my phone product I'd ,imei etc.... Previously I unlocked my boot loader through the dload process local update.... Plz help me I'm stuck....
saquib996 said:
Hey bro while flashing lollipop ROM emui 3.1 in my huawei p7 it got stuck in boot loader , so I thought to revert it back to the stock ROM and I backed up my stock ROM through twrp but when I restored it It again locked my boot loader plus its stuck in boot screen... What do I do.... How am I supposed to unlock my boot loader without knowing my phone product I'd ,imei etc.... Previously I unlocked my boot loader through the dload process local update.... Plz help me I'm stuck....
Click to expand...
Click to collapse
Hi,
i guess you have to unlock your bootloader per dload again. You can force an local update by pressing power and volume plus/minus at the same time.
Is the bootloader unlocking local update based on emui2.3? If so, you'd had to downgrade to emui 2.3 (B1xx).
To do so: Flash the downgrade packages(B8xx) first, after that the full rom(B6xx) , then the next downgrade package(B6xx) and the next rom(B1xx).
Probably your phone will boot after the first full rom flash. If it does, you could get the numbers you need, and unlock per fastboot.
l3Nni said:
Hi,
i guess you have to unlock your bootloader per dload again. You can force an local update by pressing power and volume plus/minus at the same time.
Is the bootloader unlocking local update based on emui2.3? If so, you'd had to downgrade to emui 2.3 (B1xx).
To do so: Flash the downgrade packages(B8xx) first, after that the full rom(B6xx) , then the next downgrade package(B6xx) and the next rom(B1xx).
Probably your phone will boot after the first full rom flash. If it does, you could get the numbers you need, and unlock per fastboot.
Click to expand...
Click to collapse
but bro the fact is i dont have acess to phone's internal memory how am i supposed to do... will the local update works through memory card...... i looked every thread n every posts but didnt find any solutions...... plus if i try to unlock boot from huawei official site it is demanding product id but since my phone is stuck i cant know my product id...
and thnxxx bro for ur reply....
saquib996 said:
but bro the fact is i dont have acess to phone's internal memory how am i supposed to do... will the local update works through memory card...... i looked every thread n every posts but didnt find any solutions...... plus if i try to unlock boot from huawei official site it is demanding product id but since my phone is stuck i cant know my product id...
and thnxxx bro for ur reply....
Click to expand...
Click to collapse
Yes, you could just put the update file into a folder named 'dload' in the root directory of your sd card.
l3Nni said:
Yes, you could just put the update file into a folder named 'dload' in the root directory of your sd card.
Click to expand...
Click to collapse
thankxxx bro... ur method worked.... but guess im not lucky enough because now in the update mode its showing battery less than 15% cant update.... and in bootloader i cant charge my phone, the moment i plug in the charger it automatically switch on the device and shows boot failed press volume down button to open bootloader mode.... and my phone's battery start draining instead of charging.... any help with that.... i tried to open the back cover to charge the battery externally, some how youtube taught me to open it but its conneted circuit based and cant recharge externally ..... any help:crying::crying::crying: plz.... and thanxx for ur precious time and reply ,, i deeply thank u bro for ur support..... waiting for ur further instruction.....
saquib996 said:
thankxxx bro... ur method worked.... but guess im not lucky enough because now in the update mode its showing battery less than 15% cant update.... and in bootloader i cant charge my phone, the moment i plug in the charger it automatically switch on the device and shows boot failed press volume down button to open bootloader mode.... and my phone's battery start draining instead of charging.... any help with that.... i tried to open the back cover to charge the battery externally, some how youtube taught me to open it but its conneted circuit based and cant recharge externally ..... any help:crying::crying::crying: plz....
Click to expand...
Click to collapse
You could try to boot to recovery pressing power and volume-. Does the battery charge then? I'd try myself, but my mum got my P7.. If it doesn't work you may try this script: http://forum.xda-developers.com/showthread.php?t=1658084. And if that all fails you could purchase a new battery as your final option.
Please don't try to charge your phone externally. Handling with LiOn-batterys without knowing exactly what you do could be quite dangerous.
saquib996 said:
and thanxx for ur precious time and reply ,, i deeply thank u bro for ur support..... waiting for ur further instruction.....
Click to expand...
Click to collapse
You're very welcome, I'm glad when I could help.
l3Nni said:
You're very welcome, I'm glad when I could help.
Click to expand...
Click to collapse
Bro some how my phone got charged I plugged it for the whole night and it got charged..... finally flashed with lollipop emui 3.1....
And bro sorry to bother u since u use p7 I wanted to ask that is cynogen mod available for p7 if yes then how should I flash it... I got B832 emui 3.1 and android version 5.1.1..... any idea about cynogen mod or any other rom... which one should be better....
saquib996 said:
Bro some how my phone got charged I plugged it for the whole night and it got charged..... finally flashed with lollipop emui 3.1....
And bro sorry to bother u since u use p7 I wanted to ask that is cynogen mod available for p7 if yes then how should I flash it... I got B832 emui 3.1 and android version 5.1.1..... any idea about cynogen mod or any other rom... which one should be better....
Click to expand...
Click to collapse
There are no custom roms for lollipop, unfortunately. So you have to stick with the stock one.
l3Nni said:
There are no custom roms for lollipop, unfortunately. So you have to stick with the stock one.
Click to expand...
Click to collapse
Ok bro thanx for the information....... gud bye take care....
saquib996 said:
There are no custom roms for lollipop, unfortunately. So you have to stick with the stock one.
Click to expand...
Click to collapse
Bro are u indian...?
Coz is there any option to change network frequency band coz in india I cannot use 4g because of network band.... plz help if u are indian u must be aware of jio network I cant use it in my phone... waiting for your reply.....
Hi. I am in the UK and have the first gen moto x. i was dicking around with roms etc and i ended up accidentally erasing internal storage. I managed to the get the phone back to how it was apart from the fact that it cannot make calls, text, get 3g signal. it is essentially a small tablet. when i use the dialler code to show the imei number it is 0. i tried reinstalling modems etc and none have worked. i have tried differnet roms and even flashing lollipop. I am wondering if the modems files i am using are not working because they are US files and I need some kind of EU file? Idk.
I had my imei written down so i was going to try and change it to that on the phone but engineer tools does not open or even seem to exist on the phone. i cant try using the stock rom etc because it is on a site (something like sbf developers ) that says it is forbidden. i literally have tried everything. can anyone help? :crying:
azerouz said:
Hi. I am in the UK and have the first gen moto x. i was dicking around with roms etc and i ended up accidentally erasing internal storage. I managed to the get the phone back to how it was apart from the fact that it cannot make calls, text, get 3g signal. it is essentially a small tablet. when i use the dialler code to show the imei number it is 0. i tried reinstalling modems etc and none have worked. i have tried differnet roms and even flashing lollipop. I am wondering if the modems files i am using are not working because they are US files and I need some kind of EU file? Idk.
I had my imei written down so i was going to try and change it to that on the phone but engineer tools does not open or even seem to exist on the phone. i cant try using the stock rom etc because it is on a site (something like sbf developers ) that says it is forbidden. i literally have tried everything. can anyone help? :crying:
Click to expand...
Click to collapse
Hey! If you've installed a US ROM, you are using the wrong baseband files to access your service provider network ( XT1053- US ; XT1052- UK)
Try installing an XT1052 based rom and report back . Also, be careful while flashing your new chosen ROM. Ensure that it does not downgrade / modify your current bootloader as you may end up bricking your phone (since you've upgraded to LP)
Best of luck mate .
Bhargav4591 said:
Hey! If you've installed a US ROM, you are using the wrong baseband files to access your service provider network ( XT1053- US ; XT1052- UK)
Try installing an XT1052 based rom and report back . Also, be careful while flashing your new chosen ROM. Ensure that it does not downgrade / modify your current bootloader as you may end up bricking your phone (since you've upgraded to LP)
Best of luck mate .
Click to expand...
Click to collapse
Ty for the reply. I just tried flashing a rom for the 52 instead of the 53 and twrp gives an error message of "This package is for the device: xt1052 ghost, xt1052 ghost etc.. this device is ." the etc is just a couple more models but the device doesnt seem to know what it is? its saying becuase it is for the 52 it cannot install even though the device is the 52.
azerouz said:
Ty for the reply. I just tried flashing a rom for the 52 instead of the 53 and twrp gives an error message of "This package is for the device: xt1052 ghost, xt1052 ghost etc.. this device is ." the etc is just a couple more models but the device doesnt seem to know what it is? its saying becuase it is for the 52 it cannot install even though the device is the 52.
Click to expand...
Click to collapse
Strange . Do elaborate as to what rom you are flashing and which rom you are currently using (The one that has a problem).
Also, are you wiping the system before flashing ?
Bhargav4591 said:
Strange . Do elaborate as to what rom you are flashing and which rom you are currently using (The one that has a problem).
Also, are you wiping the system before flashing ?
Click to expand...
Click to collapse
Hi again. i googled xt1052 rom and found a few. the one i tried was cyanhacker(obviously based on cm). after i got that error i tried editing the updater script to skip over the process in which it checks what device it is on. after that it appeared to flash successfully but when i tried to boot it showed the bootloader unlocked screen, vibrated then restarted and just kept doing that bootloop.
azerouz said:
Hi again. i googled xt1052 rom and found a few. the one i tried was cyanhacker(obviously based on cm). after i got that error i tried editing the updater script to skip over the process in which it checks what device it is on. after that it appeared to flash successfully but when i tried to boot it showed the bootloader unlocked screen, vibrated then restarted and just kept doing that bootloop.
Click to expand...
Click to collapse
1. Please download the correct ROM for your device from here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
2. Head over here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 and follow the Instructions. CAUTION: If you decide yourself for manual flashing DO NOT PASTE THIS CODE:
Code:
fastboot oem config carrier vzw
Or you'll end up, like me: http://forum.xda-developers.com/moto-x/moto-x-qa/carrier-retail-devices-t3174988
In case I could help you with some guidance, I would be happy, if you could help me, in my thread.
//EDIT: Your battery should be on 70% or more, before you try to do anything! Keep this in mind, else flashing could be interrupted!
Kind regards
Xanthales said:
1. Please download the correct ROM for your device from here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
2. Head over here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 and follow the Instructions. CAUTION: If you decide yourself for manual flashing DO NOT PASTE THIS CODE:
Code:
fastboot oem config carrier vzw
Or you'll end up, like me: http://forum.xda-developers.com/moto-x/moto-x-qa/carrier-retail-devices-t3174988
In case I could help you with some guidance, I would be happy, if you could help me, in my thread.
//EDIT: Your battery should be on 70% or more, before you try to do anything! Keep this in mind, else flashing could be interrupted!
Kind regards
Click to expand...
Click to collapse
Thankyou so much. did what you said. tinkered in twrp. flashed a lollipop rom and made a call. My man right here <3
azerouz said:
Thankyou so much. did what you said. tinkered in twrp. flashed a lollipop rom and made a call. My man right here <3
Click to expand...
Click to collapse
No problem, im glad to hear, that I could help you!
Maybe you can help me here?: http://forum.xda-developers.com/moto-x/moto-x-qa/carrier-retail-devices-t3174988
This would be awesome, if you got a retail device!
My phone is totally bricked not even opening in bootloader. It's only recognized by pc as "qhsusb_bulk". so I signed my phone with "Riff BOX JTAG drivers Driver Signature Enforcement Overrider". after this my phone is recognized as "Qualcomm HS-USB QLoader 9008" under Ports (COM & LPT). Then I extract Motorola qboot utility and then run blank-flash.bat file after that this is showing (flashing singleimageFAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet).
maybe that singleimage.bin file is problematic.
So I need correct blank-flash file for my phone.
Help me guys. thanks in advance.
deleted. Reason : OP edited.
sagar846 said:
Have you tried giving it CPR? (jk)
Just reflash stock firmware.
Link : Click Here
Click to expand...
Click to collapse
edit..
zman01 said:
Very useful post.. Did you read the OP or you're just guessing here?
Click to expand...
Click to collapse
Op edited post. Before there was only hard brick problem given (when I posted).
Well, there is a good chance that you can't do anything about it. But, give as some info about what you did to it, what was the last version of Android or Rom on it, and so on.
Addy K said:
My phone is totally bricked not even opening in bootloader. It's only recognized by pc as "qhsusb_bulk". so I signed my phone with "Riff BOX JTAG drivers Driver Signature Enforcement Overrider". after this my phone is recognized as "Qualcomm HS-USB QLoader 9008" under Ports (COM & LPT). Then I extract Motorola qboot utility and then run blank-flash.bat file after that this is showing (flashing singleimageFAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet).
maybe that singleimage.bin file is problematic.
So I need correct blank-flash file for my phone.
Help me guys. thanks in advance.
Click to expand...
Click to collapse
I get the same place in my moto g 2014 xt1069. Do i have any chance to create a blackflash from original lollipop ROM?
EDIT: blankflash*
marcoslucianops said:
I get the same place in my moto g 2014 xt1069. Do i have any chance to create a blackflash from original lollipop ROM?
Click to expand...
Click to collapse
Nope, you don't have any
Addy K said:
...
Click to expand...
Click to collapse
Can you give me the files you used?
Well this guide might work for you guys. Its for the moto g1 but everything used in the guide is kind of the same for all moto devices except the firmware. Don't forget to download the correct firmware for your phone :
Click Here
sagar846 said:
Well this guide might work for you guys. Its for the moto g1 but everything used in the guide is kind of the same for all moto devices except the firmware. Don't forget to download the correct firmware for your phone :
Click Here
Click to expand...
Click to collapse
This won't work, ^^ the "blank flash" in the tutorial you've sent us, is only for the Moto G 1st gen, i've already tried it ^^ this is not compatible :/
This is why we need the blank flash for the Moto G 2014, then this tuto will work ^^
Miiick3y said:
This won't work, ^^ the "blank flash" in the tutorial you've sent us, is only for the Moto G 1st gen, i've already tried it ^^ this is not compatible :/
This is why we need the blank flash for the Moto G 2014, then this tuto will work ^^
Click to expand...
Click to collapse
Check the firmware download link again (file factory). There are 5+ pages. Find the right firmware for your phone (Itll be labelled TITAN CFL blah blah)
Flash it.
Direct link : Click Here
sagar846 said:
Check the firmware download link again (file factory). There are 5+ pages. Find the right firmware for your phone (Itll be labelled TITAN CFL blah blah)
Flash it.
Direct link : Click Here
Click to expand...
Click to collapse
Thanks for help, but i can't flash anything, my phone is only recognized on my pc as a qualcomm communication port ^^
Addy K said:
My phone is totally bricked not even opening in bootloader. It's only recognized by pc as "qhsusb_bulk". so I signed my phone with "Riff BOX JTAG drivers Driver Signature Enforcement Overrider". after this my phone is recognized as "Qualcomm HS-USB QLoader 9008" under Ports (COM & LPT). Then I extract Motorola qboot utility and then run blank-flash.bat file after that this is showing (flashing singleimageFAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet).
maybe that singleimage.bin file is problematic.
So I need correct blank-flash file for my phone.
Help me guys. thanks in advance.
Click to expand...
Click to collapse
@Andy K
Found the reason why it didn't work. That is because that method is used to rescue Qualcomm Snapdragon devices. Our device is Qualcomm based so yeah. Here's a kinda detailed explanation
Owners of Qualcomm based LG’s, HTC’s, Samsung’s, Sony’s and Motorola’s, im afraid this tool is not suitable for you, because those liers mostly have chosen not to use default options of this platform, they dont (cant) want us to rescue our phones so easly, what would have happened to their service centers all around the world then ? They need to change “The Motherboard” in spite of the ability to fix this problem so easly to earn more and more and more money.
Site Link : Click Here
I was on stock Marshmallow 6.0 rom. Then I flashed stock Lollipop 5.0.2 rom in my phone and then I was updating my phone to new stagefright patch but after switch off my phone didn't turn on again.
My last android version was Marshmallow 6.0. I downgraded my phone to Lollipop 5.0.2 and tried to update latest stagefright patch from system update. But after switched off my phone never turn on again. Whenever I connect my phone to the charger it's shows nothing but white led light for 10 seconds. And my phone recognised by my PC as "qshusb_bulk".
Need Moto G 2nd Gen "blankflash image" to flash new bootloader.
As the bootloader of my phone has been collapsed so I need to flash a new bootloader to my phone to relive. But I don't have the right file. And I don't think there is any blankflash image of my phone (XT1068) is available on the net. So I just need to know that is there any way to extract these file from Stock ROM?
Addy K said:
As the bootloader of my phone has been collapsed so I need to flash a new bootloader to my phone to relive. But I don't have the right file. And I don't think there is any blankflash image of my phone (XT1068) is available on the net. So I just need to know that is there any way to extract these file from Stock ROM?
Click to expand...
Click to collapse
No there is no way. I think they already got 5.0 singleimage, but the problem is with programmer.mbn. Without motorola signature it won't flash the bootloader..
still no hope...
Do you have 5.0 or 6.0 singleimage file?
am stuck in the same position. the company has to come up with the new bootloader file. or upload the xt1068 bootloader. one method is throught riff jtag . but very few repair guys have that box. in mumbai they charge 1000-1500rs to repair such phones
I get this error on my moto x dev edition with verizon xt1060 in fastboot. i cant flash any images. i was told to use rsd lite but it doesnt detect my phone.
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
RandyThor said:
I get this error on my moto x dev edition with verizon xt1060 in fastboot. i cant flash any images. i was told to use rsd lite but it doesnt detect my phone.
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
Click to expand...
Click to collapse
Do you install Motorola drivers..?
Salik Iqbal said:
Do you install Motorola drivers..?
Click to expand...
Click to collapse
yes the newest drivers are installed. It shows up in device manager as "MOT Single ADB Interface". I can also detect it in fastboot, though most commands won't work.
i had a similar kind of problem on my ghost. Firmware crash, due to which phone was stuck at the bootloader. No recovery nor did any fastboot worked at that time. I referred this and this. It worked for me.
varunpilankar said:
i had a similar kind of problem on my ghost. Firmware crash, due to which phone was stuck at the bootloader. No recovery nor did any fastboot worked at that time. I referred this and this. It worked for me.
Click to expand...
Click to collapse
when following the second link steps i get stuck at step 8. Im not sure what he means by click on the device. does he mean the 'Mot Single ADB Interface' device? i clicked properties on that then i clicked update and i selected the folder where i kept the signed sys files. there was nothing about QHSUSB_DLOAD as it said in the tutorial though. anyway afterwards there was no port called Qualcomm HS-USB QDLoader 9008 so i couldn't get a portnumber to continue the process.
The other link you gave i assumed id go to Moto X BE\1_Repair_Boot (RSD Lite)\1060 and flash the gpt.bin and the motoboot.img but i got this error:
C:\Users\Jake\Desktop\New folder\Moto X BE\1_Repair_Boot (RSD Lite)\1060>mfastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.290s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.210s
C:\Users\Jake\Desktop\New folder\Moto X BE\1_Repair_Boot (RSD Lite)\1060>mfastboot flash motoboot motoboot.img
sending 'motoboot' (1604 KB)...
OKAY [ 0.420s]
writing 'motoboot'...
Motoboot: Unknown partition name
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.700s
I'm in basically the same situation with my XT1060 Developer Edition. Tried a long list of fixes, none has done the trick. All I have available is the fastboot menu. Phone won't boot into OS, won't go into recovery, hasn't accepted any flashes or erases. This happened because after downgrading to 4.4.4 I allowed an OTA update to 5.1. Phone rebooted and hasn't left the flashboot menu since. I, too, am looking for any help I can get on the matter.
Just like you, I tried that trick involving the fancy drivers, but my phone shows up as "Mot Single ADB Interface" in device manager, so that fix doesn't apply. If my phone reported as QHSUSB_DLOAD in device manager, it would be a different story. Though my phone was rooted and unlocked before downgrading to 4.4.4, at this point it's locked (happened without my knowledge), which I believe is why I can't reflash a recovery image.
It seems pretty clear to me that the phone has either an absent or corrupted partition scheme, as gpt.bin won't flash AND my phone doesn't acknowledge the existence of partitions. I suspect my phone began writing the 5.1 OTA update before erroring out, thus leaving me in a limbo mode halfway between 5.1 and 4.4.4. If anyone out there has experience with this seemingly unique brick situation, I would appreciate it. OP, good luck with your phone.
OrlandoAlex said:
I'm in basically the same situation with my XT1060 Developer Edition. Tried a long list of fixes, none has done the trick. All I have available is the fastboot menu. Phone won't boot into OS, won't go into recovery, hasn't accepted any flashes or erases. This happened because after downgrading to 4.4.4 I allowed an OTA update to 5.1. Phone rebooted and hasn't left the flashboot menu since. I, too, am looking for any help I can get on the matter.
Just like you, I tried that trick involving the fancy drivers, but my phone shows up as "Mot Single ADB Interface" in device manager, so that fix doesn't apply. If my phone reported as QHSUSB_DLOAD in device manager, it would be a different story. Though my phone was rooted and unlocked before downgrading to 4.4.4, at this point it's locked (happened without my knowledge), which I believe is why I can't reflash a recovery image.
It seems pretty clear to me that the phone has either an absent or corrupted partition scheme, as gpt.bin won't flash AND my phone doesn't acknowledge the existence of partitions. I suspect my phone began writing the 5.1 OTA update before erroring out, thus leaving me in a limbo mode halfway between 5.1 and 4.4.4. If anyone out there has experience with this seemingly unique brick situation, I would appreciate it. OP, good luck with your phone.
Click to expand...
Click to collapse
For both of you.. @RandyThor and @OrlandoAlex check thread after 12hrs.. i have something for you which may hopefully fix thay issue.
I'm in the same boat. At least I've finally learned why I always refuse OTA updates (until now it hadn't really dawned on me that I had to blankflash because I downgraded after having updated official firmware).
A solution would be much appreciated, as nothing I've done has worked to this point. I'll read more on here to see whether someone has already posted a solution, and I should be able to check back on this thread in a couple of hours.
EDIT:
It does not look like there is a common solution, from what I can tell in the Q&A. Will search elsewhere next.
PiArc said:
I'm in the same boat. At least I've finally learned why I always refuse OTA updates (until now it hadn't really dawned on me that I had to blankflash because I downgraded after having updated official firmware).
A solution would be much appreciated, as nothing I've done has worked to this point. I'll read more on here to see whether someone has already posted a solution, and I should be able to check back on this thread in a couple of hours.
EDIT:
It does not look like there is a common solution, from what I can tell in the Q&A. Will search elsewhere next.
Click to expand...
Click to collapse
Was busy and forgot that sorry, i put alarm for that now will update this thread in some hours.
Salik Iqbal said:
Was busy and forgot that sorry, i put alarm for that now will update this thread in some hours.
Click to expand...
Click to collapse
No worries. Whenever you get the chance.
RandyThor said:
No worries. Whenever you get the chance.
Click to expand...
Click to collapse
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
@Salik Iqbal, you've done it! Can you tell me exactly why that worked? Which version of the bootloader was that? Also, THANK YOU!
PiArc said:
@Salik Iqbal, you've done it! Can you tell me exactly why that worked? Which version of the bootloader was that? Also, THANK YOU!
Click to expand...
Click to collapse
It was from att latest firmware gpt and aboot.
Salik Iqbal said:
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Click to expand...
Click to collapse
you are the GOAT my friend
Salik Iqbal said:
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Click to expand...
Click to collapse
One last thing. The phone is working fine now but recovery doesn't seem to work. I've tried reflashing it and it works but when i enter recovery i just get that dead android guy with the error symbol. Any ideas?
RandyThor said:
One last thing. The phone is working fine now but recovery doesn't seem to work. I've tried reflashing it and it works but when i enter recovery i just get that dead android guy with the error symbol. Any ideas?
Click to expand...
Click to collapse
Oh nevermind i apologize. My recovery was working fine i forgot i have to hold vol up and tap power to get to the recovery options...
Anyway thanks again you're a life saver!!!!!
RandyThor said:
Oh nevermind i apologize. My recovery was working fine i forgot i have to hold vol up and tap power to get to the recovery options...
Anyway thanks again you're a life saver!!!!!
Click to expand...
Click to collapse
So lets close the thread by requesting moderator..
Salik Iqbal said:
So lets close the thread by requesting moderator..
Click to expand...
Click to collapse
do i have to do that lol? im a noob
I was installing EliteRom v4 but data partition was damaged and i could not change its filesystem to f2fs and I rebooted then and got the eRecovery telling data partition is damaged so i pressed "fix". it rebooted and now i cant access twrp or , just huawei software update and eRecovery, eRecovery pops up when booting without any key combinations, just power button. Any help? EDIT: FASTBOOT IS ACCESIBLE
Deleted post
EeliX7 said:
Okay, found another post and used its info to solve this.
Click to expand...
Click to collapse
Link to the post please which helped you to solve your problem?
It may be helpful for others
I was way too fast in editing that post didnt solve my problem as i cant turn usb debuggin on (was off at the moment i was installing) and the command line gives an error "remote:command not allowed" when attempting to unbrick by flashing system, boot, cust and recovery img (sorry for his terrible writing im on my tablet that is antique lags like hell even tho i have cm13)
EeliX7 said:
I was way too fast in editing that post didnt solve my problem as i cant turn usb debuggin on (was off at the moment i was installing) and the command line gives an error "remote:command not allowed" when attempting to unbrick by flashing system, boot, cust and recovery img (sorry for his terrible writing im on my tablet that is antique lags like hell even tho i have cm13)
Click to expand...
Click to collapse
So you are still stuck? Need help?
Well I sent the phone to repair due to TRUE laziness... So I don't need help with that anymore, thanks anyway
EeliX7 said:
Well I sent the phone to repair due to TRUE laziness... So I don't need help with that anymore, thanks anyway
Click to expand...
Click to collapse
I hope the tech repair guys fixes it. :angel:
sniperlife:D said:
I hope the tech repair guys fixes it. :angel:
Click to expand...
Click to collapse
Well they are equipped to fix this
shashank1320 said:
Well they are equipped to fix this
Click to expand...
Click to collapse
Yes. But I experienced tech guys before who were new to a certain problem. They were not able to fix it then.
Back in 2011 when I was a kid, it took 2 weeks to "repair" my bricked tab. The tab travelled over 400 kilometres!
THIS REPLY IS THE 3000th post in Honor 5C QnA
EeliX7 said:
THIS REPLY IS THE 3000th post in Honor 5C QnA
Click to expand...
Click to collapse
Good achievement:good:
Goes to show how active honor forums are.
sniperlife:D said:
Goes to show how active honor forums are.
Click to expand...
Click to collapse
More than active...lol.
This is since honor 5X development started to get boost. People came to honor forum
lol the people on the goddamn service centre actually thought there was warranty left... FREE REPAIR!
EeliX7 said:
lol the people on the goddamn service centre actually thought there was warranty left... FREE REPAIR!
Click to expand...
Click to collapse
Thats cool. I got mine extended for 6 months when i relocked bootloader and no one could identify lol.