I softbricked my phone with the Overclock method, so I am trying to reflash it. RSD Lite does not and has never worked for me. Last time I had to use fastboot.
I tried the same commands as before with fastboot, but when I get to fastboot flash system system.img, I get this error:
(bootloader) Preflash validation failure
FAILED (remote)
finished total time 24.331 s
And now on my phone it says:
AP Fastboot Flash Mode (S) (Flash Failed)
Weird that you can't get RSD to work, are you on windows if so what version?
JRW 28 said:
Weird that you can't get RSD to work, are you on windows if so what version?
Click to expand...
Click to collapse
Windows 7 64 Bit.
I did a search for preflash validation failure, and found this thread:
http://forum.xda-developers.com/showthread.php?t=1493386
I'm going to try the motofastboot.exe with boot.img, but right now it's saying my battery is too low.
Will it even charge without the system being able to come up?
Moverf16 said:
Windows 7 64 Bit.
I did a search for preflash validation failure, and found this thread:
http://forum.xda-developers.com/showthread.php?t=1493386
I'm going to try the motofastboot.exe with boot.img, but right now it's saying my battery is too low.
Will it even charge without the system being able to come up?
Click to expand...
Click to collapse
Very weird that you can't get it to work in win7.
You def need to charge it. See if you can get it to try n boot up regularly then pull the battery and plug it in with the battery back in it. Hopefully it will charge if not you will have to do the MacGyver mod
JRW 28 said:
Very weird that you can't get it to work in win7.
You def need to charge it. See if you can get it to try n boot up regularly then pull the battery and plug it in with the battery back in it. Hopefully it will charge if not you will have to do the MacGyver mod
Click to expand...
Click to collapse
What's the MacGyver mod?
Also, what's the RZR mod that allows me to boot into the Bootstrapper to restore? That would've helped out with my overclocking experimentation gone awry.
Moverf16 said:
What's the MacGyver mod?
Also, what's the RZR mod that allows me to boot into the Bootstrapper to restore? That would've helped out with my overclocking experimentation gone awry.
Click to expand...
Click to collapse
MacGyver method...
Here's the RAZR cwm on boot. Just follow all the directions, replace the razr bootstrap with the a2 bootstrap.
Ok, while the phone is charging I've been doing some more searching but I can't find anything on the preflash validation failure (a fix for it, anyway).
Any ideas if the moto-boot.exe and boot.img doesn't work?
I know you've probably tried a lot to get RSD working bit it would save you a lot of headaches if we could figure out what's wrong and get it working for you
Ok, got it flashed and working again. However, now it still boots into AP Fastboot every time.
Any ideas?
And even after reboot Atrix 2 Bootstrapper does a force close.
And Rom Manager can't fix permissions:
An error occurred while attempting to run privileged commands!
Ok, I found that by doing a Titanium Backup restore on Atrix Bootstrapper, I was able to get it working.
However, because my phone now defaults to the Fastboot screen, it reboots into AP Fastboot instead of CWM recovery.
If you can get into bootstrap flash a backup
JRW 28 said:
If you can get into bootstrap flash a backup
Click to expand...
Click to collapse
Trying that now as part of my restore (going back to Supercharged V5, plus the update, plus restoring my data).
I'm also thinking if I get a full charge and maybe just hook it up to Fastboot and send it a BS command, it'll come out of the fastboot fail mode and boot normally.
If you're stock on Fastboot:
Press power so the screen cuts off
Hold volume up and down buttons
Hold power until it cuts on with the menu
Press volume up to boot normally
Mine goes to the same screen every time I shut down too, even when I try to boot into CWM I have to do this, but it should get you up and running for the time being.
Sent from my MB865 using Tapatalk
I can get it to boot normally, but I just want it to stop going directly into AP Fastboot (Flash Fail) every time it reboots.
I'm not even sure what caused it to start doing this.
Ok based on the Fastboot Wiki http://android-dls.com/wiki/index.php?title=Fastboot
I think the problem is caused because of a lack of recovery.img
I flashed the boot.img from the Invalid CG thread with no problem using moto-fastboot which allowed me to flash the system and preinstall to get it working again.
Now I think it's booting in AP fastboot every time because the recovery is gone.
When I try to flash recovery.img, it says INFOPreflash validation failure.
In my research I have found that this is because of an unsigned or recognized IMG file, but I'm using the one from the noob thread.
Any help would be appreciated. If I can get the phone to boot normally every time, everything will be perfect.
same thing happened to me , i cant flash a fxz. it keeps saying failure, when i reboot it boots into flash mode if i pull the battery and hold vol up and down and power go to boot normal i can get into my phone so its not completely screwed but i would like to find a solution
Moverf16 lets figure out what gremlins you have so we can get RSD working for you. I know you tried more then enough but if we can get it working for you all your headaches will be gone.
JRW 28 said:
Moverf16 lets figure out what gremlins you have so we can get RSD working for you. I know you tried more then enough but if we can get it working for you all your headaches will be gone.
Click to expand...
Click to collapse
+1
-Reboot your computer
-Uninstall any Motorola drivers you've installed
-Uninstall RSD Lite
-Reboot your computer
-Install these Motorola drivers.
-Reboot your computer
-Install RSD Lite
-Reboot your computer
-Boot your phone into Fastboot mode
-Connect your phone to your computer using a high-quality (preferably OEM) cable.
-Let your PC install any necessary drivers. When it finishes it should tell you that the device "Fastboot Edison S" is ready for use.
-Turn your phone off, disconnect the cable
-Reboot your computer
-Boot your phone back into Fastboot mode
-Wait a couple seconds then connect your phone to your computer
-Wait a couple more seconds, then look at the bottom text that's displayed on your phone. It should say
Transfer Mode:
USB Connected
Click to expand...
Click to collapse
This means that your phone is connected to your computer.
-Open up RSD Lite
-Wait a couple seconds. At the top of the list should be your phone (under model it should say "Fastboot Edison S")
-If you've done all this and everything has worked out for you, flash the fxz! Make sure to follow the instructions in the noob thread as specifically as possible.
good afternoon forum Mods if I'm posting in the wrong section I'm sorry and move where it should be post it at I couldn't find a way to open a new thread under Motorola all I was able to see was threads already posted
any way I'm in desperately need of help I have this Motorola XT910 which one was working just fine the only problem that it had was the wifi and bluetooth wouldn't turn on it's a LATAM device and it had 4.1.2 I don't know who updated to this version or how that's all I could see under about phone it has bootloader locked I couldn't tell you if it was root don't really remember I only had it for a couple hrs and decided to flash a different rom to see if the wifi and bluetooh option would be available
this is what I done to the phone so far i'm gonna start from when it was working
I install BMM and I follow all the instructions just like in this post http://forum.xda-developers.com/showthread.php?t=2260951 but phone never booted normally it just got stock on this screen with a gear looking wheel turning I did a back up of my system but could never go to it all i remember being able to go to was this screen on BMM where you can chose what system you want to boot but all I see was artmod rom and all the other system windows were empty so i was just stuck between this screen the gear wheel trying to boot the system and the screen where i could chose the system i wanted to boot into
no help there so battery was low so i removed it charged it with a universal charger over night boot into AP Fastboot and trying flashing the 3 folowing roms with RSD Lite 6.1.4 but every rom gives me the same error message CDT.BIN failed phone return fail
these are the roms i'm trying to flash
Branding: Retail Brazil
Version:9.8.2O-124_SPUL-17 Service
Android Version:4.1.2
with RSD Lite 6.1.4
Branding: Oi Brazil
Version:9.8.2O-124_SPUL-17 Service
Android Version:4.1.2
with RSD Lite 6.1.4
and one from UK with version 4.1.2 as well and no go also i have tried this flash tool HSD-pilots UNBRICK but always gives me error message when trying to flash the booteujb.img file i tried doing directely and as follow
1) download These fastboot files.rar (clink on text)
2)download retailEU. jellybean OTA
3)Download HSD-pilots UNBRICK.rar
4)UNRAR HSD-pilots UNBRICK.rar from step (3) to any new folder (lets name it UNBRICK)
5) UNRAR Fastboot files:
cdrom_signed
cdt.bin_signed
devtree_signed
ebr_signed
mbr_signed
recovery_signed
radio.img
system_signed
from step (1) to Folder from step (4) we named UNBRICK ONLY extract files i said
6)Connect your device to pc
7)open UNBRICK folder Hold shift and right click on white space -> then press OPEN COMMAND WINDOW HERE
8)flash files from step (5) by writing in the command window you opened:
mfastboot flash cdrom cdrom_signed
mfastboot flash cdt.bin cdt.bin_signed
mfastboot flash devtree devtree_signed
mfastboot flash ebr ebr_signed
mfastboot flash mbr mbr_signed
mfastboot flash recovery recovery_signed
mfastboot flash radio radio.img
9)with the phone still connected to PC open UNBRICK folder and tun Unbrick.bat.
10) after unbrick.rar flashed press power button once, and immediately hold volume up + volume down and press power again
11) go down to recovery and press volume up
12) when you just follow instructions in bat file. see android picture press volume down and volume up at the same time and wait for radio to install
13) after installation of radio wipe data and catch -> navigate to factory reset and do it
14) Then go to install update from external memory and install retailEU. jellybean OTA that you downloaded (you have to put it to your external SD card)
15) If all is fine it will update, just reboot and its unbricked
no luck what else can you suggest please any help would be really appreciated
sorry buddy but i didn't read all of your post. cuz i know it. if you can't flash your phone using fastboot recovery bootloader mode and ect... you need to flash using J-TAG or BOX , normal users doesn't have these tools, mobile fixers have these... that is the very last way of flashing...
if i helped you press THANKS button
m3ni said:
sorry buddy but i didn't read all of your post. cuz i know it. if you can't flash your phone using fastboot recovery bootloader mode and ect... you need to flash using J-TAG or BOX , normal users doesn't have these tools, mobile fixers have these... that is the very last way of flashing...
if i helped you press THANKS button
Click to expand...
Click to collapse
I know what J-TAG is but when you say box what box are you talking about?
also what is this error I keep getting in RSD Lite CDT.BIN phone returned fail I couldn't find any useful information on the web or here
re
prz0007 said:
I know what J-TAG is but when you say box what box are you talking about?
also what is this error I keep getting in RSD Lite CDT.BIN phone returned fail I couldn't find any useful information on the web or here
Click to expand...
Click to collapse
because no one faced that problem, even me, but i see lots of pepple failing to flash theyr phones and using j-tag, ok i don't know what is the name of box there, but here they call it box, it will cpnnect to COM1 port and a tiny box is in middle and it will connect to phone! it has its own flash tools and... the box is 20-30$ i never buy one of them, i just pey them for flashing (for some phones that i can't flash)
we can't do this, so maybe you can? i suggest you to call your mobiles caustomare care service, and tell the problom to them, they know what to dp
and i read some where that motorolla uses mtk chipsets
so try a search of " how to flash mtk phones "
it use sp flash tool, sorry
and other thing, i'm so sleepy i cant type any more, if i helped press thanks...
Hi all,
I installed the TWRP recovery for my mate 7 - 09 version, with lollipop 5.1. But then I unknowingly wiped something I shouldn't have: I think it was the system folder. No backups were made
My phone keeps starting up to the huawei logo and then reboots\turns off. I can get into fastboot&rescue mode, but that's it. No recovery, no 3-button fix (as far as I know).
The second problem is that I cannot get my device to be recognised by my pc. adb devices doesn't give me any results.
I don't feel like I can install the drivers properly as well. Pherhaps thats the problem? How can I do this? I have a driversetup from a mate7 download, but double clicking it doesnt show any prompts.
Anyone who can help me in any way is more than welcome!
dekraan said:
Hi all,
I installed the TWRP recovery for my mate 7 - 09 version, with lollipop 5.1. But then I unknowingly wiped something I shouldn't have: I think it was the system folder. No backups were made
My phone keeps starting up to the huawei logo and then reboots\turns off. I can get into fastboot&rescue mode, but that's it. No recovery, no 3-button fix (as far as I know).
The second problem is that I cannot get my device to be recognised by my pc. adb devices doesn't give me any results.
I don't feel like I can install the drivers properly as well. Pherhaps thats the problem? How can I do this? I have a driversetup from a mate7 download, but double clicking it doesnt show any prompts.
Anyone who can help me in any way is more than welcome!
Click to expand...
Click to collapse
Hey Buddy, here's what you can try to do:
1.) Boot connect your phone to your computer.
2.) Next, boot your phone to fastboot.
3.) Next, open command prompt from the folder where your ADB files are stored.
4.)On CMD type:
fastboot devices
5.) If your device appears then you have 2 options now. You can either:
a.) Flash Stock recovery.img or
b.) Flash back TWRP
6.) If choosing option a.) you can then save stock firmware within dload folder on your external sd card then force upgrade via 3 btn method.
7.) If choosing option b.) you can boot to twrp then either sideload a custom rom or try to save on your external sd and flash
blitzkriegger said:
Hey Buddy, here's what you can try to do:
1.) Boot connect your phone to your computer.
2.) Next, boot your phone to fastboot.
3.) Next, open command prompt from the folder where your ADB files are stored.
4.)On CMD type:
fastboot devices
5.) If your device appears then you have 2 options now. You can either:
a.) Flash Stock recovery.img or
b.) Flash back TWRP
6.) If choosing option a.) you can then save stock firmware within dload folder on your external sd card then force upgrade via 3 btn method.
7.) If choosing option b.) you can boot to twrp then either sideload a custom rom or try to save on your external sd and flash
Click to expand...
Click to collapse
I'll give that a try, thank you. With step 1, you just mean: connect the phone through usb to the computer, right?
When I rooted the phone, I did so on my work laptop, so I am hoping I can get it recognised there, but lets see what happens at home.
EDIT:
Ok, i've typed in fastboot devices, and it gave me one line with a 16-digit code (numbers and letters) some white space and then the word fastboot. What does that mean?
That should meen it recognizes your phone in fastboot mode. Next step is to flash as stated in step 5 that in the instructions.
Sent from my HUAWEI MT7-L09 using Tapatalk
dekraan said:
I'll give that a try, thank you. With step 1, you just mean: connect the phone through usb to the computer, right?
When I rooted the phone, I did so on my work laptop, so I am hoping I can get it recognised there, but lets see what happens at home.
EDIT:
Ok, i've typed in fastboot devices, and it gave me one line with a 16-digit code (numbers and letters) some white space and then the word fastboot. What does that mean?
Click to expand...
Click to collapse
EDIT AGAIN:
Ok, this is what I did. I downloaded the well known mate7 package, extracted the b119 tools folder and I put the twrp_2.8.7.0_mate7_5.1.img file from this forum (the TWRP for 5.1) inside this folder.
Then, I open cmd inside the folder, and I typed: fastboot flash recovery twrp_2.8.7.0_mate7_5.1.img. This is what happens:
target reported max download size of 471859200 bytes
sending 'recovery'(12644 KB)...
OKAY [ 1.302s]
writing 'recovery'...
OKAY [ 0.455s]
finished. total time: 1.756s
Now, I finally managed to get back into TWRP! I've only got 2% battery though (but I see a + which I think means charging...EDIT: yes, it is on 3% now. Better leave it like this...).
It tells me this:
TWRP has detected an unmodified system partition.
TWRP can leave your system partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock rom from replacing TWRP and will not offer to root your device. Installing zips or performing adb operations may still modify the system partition.
I decided to swipe, to allow modifications.
So, I've got twrp back! For lollipop. This probably means I have to flash the lollipop rom? I will download the update.zip file next and put it on my sd card (using my pc and a microsd adapter...)
Keep you posted!
Ok, this is not working.
I put update.zip on my sd-card, and tried to install it. This is what I get:
Installing 'sd-ext/update.zip'...
checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:unknown command [errno]
file_getprop: failed to stat
E: error executing updater binary in zup 'sd-ext/update.zip'
Error flashing zip 'sd-ext/update.zip'...
Updating partition details...
...done
EDIT:
I tried to sideload but on my pc I get:
error: protocol fault (no status)
And on my TWRP I get:
You need adb 1.0.32 or newer to sideload to this device.
EDIT:
Updated my adb to 1.0.32 for windows, and rebooted everything. Now i'm at 6% of sideload. Hoping this will work!
EDITn the PC everything seems to go ok, but on my phone it says: E:Zip signature verification failed:1
What should I try next?
dekraan said:
Ok, this is not working.
I put update.zip on my sd-card, and tried to install it. This is what I get:
Installing 'sd-ext/update.zip'...
checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:unknown command [errno]
file_getprop: failed to stat
E: error executing updater binary in zup 'sd-ext/update.zip'
Error flashing zip 'sd-ext/update.zip'...
Updating partition details...
...done
EDIT:
I tried to sideload but on my pc I get:
error: protocol fault (no status)
And on my TWRP I get:
You need adb 1.0.32 or newer to sideload to this device.
EDIT:
Updated my adb to 1.0.32 for windows, and rebooted everything. Now i'm at 6% of sideload. Hoping this will work!
EDITn the PC everything seems to go ok, but on my phone it says: E:Zip signature verification failed:1
What should I try next?
Click to expand...
Click to collapse
I don't advise you to flash lollipop firmware first. It's more prudent to go back to kitkat first as I believe Lollipop needs kitkat as base
1.) Put stock kitkat update.app on dload folder of your memory card. Also make sure you have the LO9 stock kitkat recovery.
2.) With your phone connected to pc, go to twrp and reboot to bootloader.
3.) Once on bootloader open cmd on your tools folder then fastboot flash the stock kitkat recovery.
4.) Once done, fastboot reboot then force upgrade to install stock firmware.
5.) Once you have stock kitkat follow the drill to reach lollipop
blitzkriegger said:
I don't advise you to flash lollipop firmware first. It's more prudent to go back to kitkat first as I believe Lollipop needs kitkat as base
1.) Put stock kitkat update.app on dload folder of your memory card. Also make sure you have the LO9 stock kitkat recovery.
2.) With your phone connected to pc, go to twrp and reboot to bootloader.
3.) Once on bootloader open cmd on your tools folder then fastboot flash the stock kitkat recovery.
4.) Once done, fastboot reboot then force upgrade to install stock firmware.
5.) Once you have stock kitkat follow the drill to reach lollipop
Click to expand...
Click to collapse
Hi, thank you for your advice. I have but one question remaining: what stock kitkat update should I use? And where can I find the right recovery that goes with it?
I've tried several recovery_stock.img I found, and it does take away TWRP, so it might have done the trick. Only problem is that I cannot force upgrade to install whats on my sd-card....The phone keeps turning on (after a long push) and after seeing the logo for a little while, it turns off (short vibration)... Is there another way?
dekraan said:
Hi, thank you for your advice. I have but one question remaining: what stock kitkat update should I use? And where can I find the right recovery that goes with it?
I've tried several recovery_stock.img I found, and it does take away TWRP, so it might have done the trick. Only problem is that I cannot force upgrade to install whats on my sd-card....The phone keeps turning on (after a long push) and after seeing the logo for a little while, it turns off (short vibration)... Is there another way?
Click to expand...
Click to collapse
You should flash B137SP03 firmware. You can also refer to this guide:
http://forum.xda-developers.com/mate-7/help/5-1-to-4-4-2-bootloop-t3132888
1.)Prepare the Stock B137SP03 firmware on your SD card
2.)Download the fastboot.zip guide and extract it to a separate folder.
3.) next connect your phone to your computer and go to fastboot mode.
4.) Flash the boot.img and recovery.img you find on that guide.
5.) Once done, do the force upgrade with the B137 firmware.
blitzkriegger said:
You should flash B137SP03 firmware. You can also refer to this guide:
http://forum.xda-developers.com/mate-7/help/5-1-to-4-4-2-bootloop-t3132888
1.)Prepare the Stock B137SP03 firmware on your SD card
2.)Download the fastboot.zip guide and extract it to a separate folder.
3.) next connect your phone to your computer and go to fastboot mode.
4.) Flash the boot.img and recovery.img you find on that guide.
5.) Once done, do the force upgrade with the B137 firmware.
Click to expand...
Click to collapse
I've followed the guide you are reffering to. And I flashed the boot and recovery, and managed to get the roll back force installed. But for the life of me, I cannot get my phone to force install the B137 zip. I just can't get into force install mode. Are there tips or tricks? I am holding power up and down, and then press power untill I feel a short vibration. But all it does it show me the huawei logo screen and then shuts down again.
Very frustrating!
EDIT:
ok, I noticed that when my sd-card is not inserted, the phone easily boots into the force install mode. It shows the logo for a couple of seconds, screen goes black and then the force install loads. So this is what I did: insert the sd card half way, press vol up and down, and power on. Then after the logo when the screen goes black, insert the sd-card all the way and when the phone goes to force install mode, it can find the update!
Now installing.... hope this helps someone else out there!
Worked! And I am up and running again! Thank you for saving my mate
I got my Mate bricked and i've been trying to figure out how to solve it. I tried lots of things from different guides, but just an hour ago I found this guide and it worked! I can't tell you how happy I am right now, thanks guys!
aleksik said:
I got my Mate bricked and i've been trying to figure out how to solve it. I tried lots of things from different guides, but just an hour ago I found this guide and it worked! I can't tell you how happy I am right now, thanks guys!
Click to expand...
Click to collapse
Glad to hear both of you guys have your mates up and running again. As long as a phone turns on and is not dead as a brick there's always hope it can be restored
Hi everyone, I have the same problem with my mate 7, i was messing with unlocking bootloader(which I succesfully have done), couldn't get my phone rooted so installed TWRP recovery for Lollipop(which was already installed when i bought the phone). Ended up with soft bricked phone(no OS, no recovery at all).
I tried different tutorials how to fix it, none of them worked(including that one unfortunatelly).
I have taken some pictures to show you what the problem is but cannot post them until reach 10 posts on forum
Basically, i can get into fastboot mode by holding volume down with power button. Windows and Hisuite don't recognise my device but in fastboot mode i can check devices connected. Typing "fastboot devices" i get "P6Q7M14A15008421 fastboot", which i guess is my device indeed.
After that i try flashing boot.img and recovery.img(which are reported OK). Then rebooting with 3 button(vol up and down, power) and Huawei logo screen appears for a bit and goes into white screen saying "rescue mode" and at the bottom: "Error Func NO: 10(FUNC_BOOT_RECOVERY) Error NO:2". Trying rebooting into recovery mode(vol up and power) it shows similar "recovery mode" screen but with different errors: "Error! Func NO:12(FUNC_LOAD_IOM3) Error NO:1".
That's it! It seems like i cannot flash my device successfully for some reason. What Windows version did you guys use?? I tried Win 8.0 and Win 10, maybe i should use older systems? Please help, i had my phone for a week only and broke it(
I can't help you much because I don't have enough knowledge about these kind of things.. I use Windows 7 and from my previous experiences I can say that working with Windows 8 can be frustrating. PS. I bricked my Mate 12hrs after buying it
muzammil84 said:
Hi everyone, I have the same problem with my mate 7, i was messing with unlocking bootloader(which I succesfully have done), couldn't get my phone rooted so installed TWRP recovery for Lollipop(which was already installed when i bought the phone). Ended up with soft bricked phone(no OS, no recovery at all).
I tried different tutorials how to fix it, none of them worked(including that one unfortunatelly).
I have taken some pictures to show you what the problem is but cannot post them until reach 10 posts on forum
Basically, i can get into fastboot mode by holding volume down with power button. Windows and Hisuite don't recognise my device but in fastboot mode i can check devices connected. Typing "fastboot devices" i get "P6Q7M14A15008421 fastboot", which i guess is my device indeed.
After that i try flashing boot.img and recovery.img(which are reported OK). Then rebooting with 3 button(vol up and down, power) and Huawei logo screen appears for a bit and goes into white screen saying "rescue mode" and at the bottom: "Error Func NO: 10(FUNC_BOOT_RECOVERY) Error NO:2". Trying rebooting into recovery mode(vol up and power) it shows similar "recovery mode" screen but with different errors: "Error! Func NO:12(FUNC_LOAD_IOM3) Error NO:1".
That's it! It seems like i cannot flash my device successfully for some reason. What Windows version did you guys use?? I tried Win 8.0 and Win 10, maybe i should use older systems? Please help, i had my phone for a week only and broke it(
Click to expand...
Click to collapse
Sounds like the wrong boot.img or recovery.img has been flashed. May I know what Mate 7 model you have and which Lollipop firmwre version your phone came last with?
Try to obtain boot.img and revoery.img for your lollipop version then flash that via fastboot
blitzkriegger said:
Sounds like the wrong boot.img -recovery.img has been flashed. May I know what Mate 7 model you have and which Lollipop firmwre version your phone came last with?
Try to obtain boot.img and revoery.img for your lollipop version then flash that via fastboot
Click to expand...
Click to collapse
My phone mt7-09l, european version 16gb. Came with lollipop 5.1 when I bought it but I think I have formatted it via twrp recovery so it shouldn't matter what boot and recovery version I am trying to flash, should it? I'll extract boot and recovery from b308 today andtry that, see if this works. If not, only thing I can try is using win7 and that's it really, no more possibilities
dekraan said:
I've followed the guide you are reffering to. And I flashed the boot and recovery, and managed to get the roll back force installed. But for the life of me, I cannot get my phone to force install the B137 zip. I just can't get into force install mode. Are there tips or tricks? I am holding power up and down, and then press power untill I feel a short vibration. But all it does it show me the huawei logo screen and then shuts down again.
Very frustrating!
EDIT:
ok, I noticed that when my sd-card is not inserted, the phone easily boots into the force install mode. It shows the logo for a couple of seconds, screen goes black and then the force install loads. So this is what I did: insert the sd card half way, press vol up and down, and power on. Then after the logo when the screen goes black, insert the sd-card all the way and when the phone goes to force install mode, it can find the update!
Now installing.... hope this helps someone else out there!
Click to expand...
Click to collapse
I'm stuck on this stage, no errors while flashing but no boot either. Shows logo then like a spark a bit of music and animation (1 sec maybe) and reboot, so on and on and on...
muzammil84 said:
My phone mt7-09l, european version 16gb. Came with lollipop 5.1 when I bought it but I think I have formatted it via twrp recovery so it shouldn't matter what boot and recovery version I am trying to flash, should it? I'll extract boot and recovery from b308 today andtry that, see if this works. If not, only thing I can try is using win7 and that's it really, no more possibilities
Click to expand...
Click to collapse
If you were on Lollipop when everything went sour, you should do what I did, thanks to advice from @blitzkriegger:
You should flash B137SP03 firmware. You can also refer to this guide:
http://forum.xda-developers.com/mate...tloop-t3132888
1.)Prepare the Stock B137SP03 firmware on your SD card
2.)Download the fastboot.zip guide and extract it to a separate folder.
3.) next connect your phone to your computer and go to fastboot mode.
4.) Flash the boot.img and recovery.img you find on that guide.
5.) Once done, do the force upgrade with the B137 firmware.
I used the full steps from the link in there: flashed the right boot and recovery through fastboot. Then I flashed the rollback zip from my sd-card, and then I flashed the B137 zip from my sd-card. I can't tell you more about it, obviously
brack11 said:
I'm stuck on this stage, no errors while flashing but no boot either. Shows logo then like a spark a bit of music and animation (1 sec maybe) and reboot, so on and on and on...
Click to expand...
Click to collapse
Been there, done that. Very frustrating! I've tried several things, none of which are probably the right way, but they worked for me. sometimes....
Can you get into stock recovery (vol+ and power)? What I tried several times was wipe cache, and then hold the powerbutton untill my phone turned off. That worked occasionally to get the device totally turned off. Then try to get to force update with your sd-card half way in, and flip it in totally when the logo dissapears and the screen is black. I also tried to shut down the constant starting up by going into fastboot/recovery mode and then holding power down. As long as it takes. Good luck! And hopefully someone can give you proper advice...
I have run into trouble using this method: https://www.youtube.com/watch?v=hb0jKB8OFko to flash stock firmware
My device: Droid Maxx
Bootloader locked, not rooted
4.4.4 at the start of the process
I downloaded the suggested firmware and ran into problems.
The first time I attempted it RSD appeared to flash everything except system.img which got hung up and the bootloader gave me a message in red stating: "no valid piv block in sp for system" This occured with the 1FF-obake-maxx_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip 1.0.0 software.
Figuring I had the incorrect firmware i tried two other roms: 1. CFC-obake-maxx_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip 1.0.0 and 2. 1FF-obake-maxx_verizon-user-4.4.4-SU6-7-release-keys.xml.zip 1.0.0. Both failed with a different error message. This time RSD and the bootloader told me "preflash validation failed for gpt".
I have tried this with RSD 6.1.5 and 6.2.4
My suspicion is that I don't have the correct firmware, but I could be wrong.
The bad news is that the phone will not boot into recovery or normally. The good news is that the phone WILL enter bootloader mode and RSD WILL recognize it.
Anyways any help would be greatly appreciated.
Stanleywinthrop said:
I have run into trouble using this method: https://www.youtube.com/watch?v=hb0jKB8OFko to flash stock firmware
My device: Droid Maxx
Bootloader locked, not rooted
4.4.4 at the start of the process
I downloaded the suggested firmware and ran into problems.
The first time I attempted it RSD appeared to flash everything except system.img which got hung up and the bootloader gave me a message in red stating: "no valid piv block in sp for system" This occured with the 1FF-obake-maxx_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip 1.0.0 software.
Figuring I had the incorrect firmware i tried two other roms: 1. CFC-obake-maxx_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip 1.0.0 and 2. 1FF-obake-maxx_verizon-user-4.4.4-SU6-7-release-keys.xml.zip 1.0.0. Both failed with a different error message. This time RSD and the bootloader told me "preflash validation failed for gpt".
I have tried this with RSD 6.1.5 and 6.2.4
My suspicion is that I don't have the correct firmware, but I could be wrong.
The bad news is that the phone will not boot into recovery or normally. The good news is that the phone WILL enter bootloader mode and RSD WILL recognize it.
Anyways any help would be greatly appreciated.
Click to expand...
Click to collapse
Okay, as long as you can enter fastboot (bootloader mode) there is hope. That's the first thing.
Since RSD recognizes your phone then there is obviously something wrong with the flashing process. You can use either the 1FF obake-maxx or CFC obake-maxx firmware. The 1FF keeps your apps and data intact while the CFC firmware wipes everything off your phone and you start clean. I would recommend using the CFC so you do not anything left over from previous flashes. Also, make sure the entire firmware file is downloaded. I got only partial downloads( like 150/200 mb) several times when I tried to download the files. Both the 1FF and CFC should be about 900 or so mb each. Exactly what steps are you following? And where are you getting your downloads from?
classic757 said:
Okay, as long as you can enter fastboot (bootloader mode) there is hope. That's the first thing.
Since RSD recognizes your phone then there is obviously something wrong with the flashing process. You can use either the 1FF obake-maxx or CFC obake-maxx firmware. The 1FF keeps your apps and data intact while the CFC firmware wipes everything off your phone and you start clean. I would recommend using the CFC so you do not anything left over from previous flashes. Also, make sure the entire firmware file is downloaded. I got only partial downloads( like 150/200 mb) several times when I tried to download the files. Both the 1FF and CFC should be about 900 or so mb each. Exactly what steps are you following? And where are you getting your downloads from?
Click to expand...
Click to collapse
Thanks for your help, but it appears that I have resolved the issue. As it turns out, the software need to be extracted to and launched from a clean folder. I had been placing it in the same folder I had adb and fastboot. My guess is that having the other version of fastboot in the same folder as the XML file confused RSD and caused the problem.
Stanleywinthrop said:
Thanks for your help, but it appears that I have resolved the issue. As it turns out, the software need to be extracted to and launched from a clean folder. I had been placing it in the same folder I had adb and fastboot. My guess is that having the other version of fastboot in the same folder as the XML file confused RSD and caused the problem.
Click to expand...
Click to collapse
Great! Glad to hear you resolved your problem. :good: