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.
Related
Hiya,
After dealing with a half-bricked Xoom, I did some research on this problem and found a solution.
If in any case, you happen to get stuck on the "Motorola Dual-Core Technology"
Solution to this (For the MZ604, One-Click rooted):
MZ604 Stock .imgs Download: http://developer.motorola.com/products/software/
*Make sure you have fastboot in the same directory as your adb for easy access*
1. Plug in your USB cord
2. Turn off your Xoom (Vol-Up + Power)
3. Boot into fastboot (Vol-Down + Power)
4. On your computer, open up a command prompt, and type the following:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
-or-
Code:
fastboot flash boot <path to boot.img>
fastboot flash system <path to system.img>
fastboot flash recovery <path torecovery.img>
fastboot flash userdata <path userdata.img>
fastboot erase cache
fastboot oem lock
5. Reboot the Xoom
Code:
fastboot reboot
6. There you go, back to stock!
On the real though, if you can get to Fastboot (or even the Moto "Android Recovery" state), you're not THAT bricked you've got to relock and go back to out-of-box; just keep a known-good boot.img around somewhere.
You just saved my life!
Thanks for sharing OP.
I take it this method is the same for 3.1?
I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Lcsglvr said:
I tried reverting back to stock using the "one click" root/unroot tool that was the first to come out for the Xoom.
Anyway, I tried the unroot process and everything was going fine, until something occurred. Now, it tries to boot up and says at the Moto Dual Core Technology screen, "Failed to boot LNX 0x0004 // Starting RSD mode 2".
Can someone help
Click to expand...
Click to collapse
Can anyone help!
Lcsglvr said:
I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Can anyone help!
Click to expand...
Click to collapse
same here, anyone help ((
Lcsglvr said:
I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Can anyone help!
Click to expand...
Click to collapse
You can still enter fastboot if you xoom won't shut off. Just hold the appropria oncete buttons as it reboot. Happened to me last night upgrading to 3.1. It. Wouldn't shut down at all. Once I got into fastboot my computer saw it and I was able to fix
Honestly, I almost went through all of this last night when my WIFI Xoom got stuck in a boot loop.
However, I noticed that when my recovery went to flash the new 3.1 file, I felt like it didn't take as long as it should have. The file was the right size and all and it even said that everything installed successfully, but it just kept boot looping regardless of trying over and over. So I went ahead and re-downloaded the 3.1 file and repeated the steps to flash it and everything worked.
So, before you spend a whole lot of time restoring your Xoom, simply re-download the files and try it one more time. It worked for me.
rebill said:
You can still enter fastboot if you xoom won't shut off. Just hold the appropria oncete buttons as it reboot. Happened to me last night upgrading to 3.1. It. Wouldn't shut down at all. Once I got into fastboot my computer saw it and I was able to fix
Click to expand...
Click to collapse
Thanks! Finally have some hope to recovering. I'll post steps I took later once I get this damn thing fixed.
hmmm... I'm in fastboot supposedly and tried to flash boot.img but it seems to be stuck at <waiting for device>
This happen to anyone else?
After search seems like a driver issue, but I have installed the drivers... I was previous rooted, so I know I have the drivers. Just to be sure, I ran the MotoHelper again. I don't understand. It's just seeing my device on the "Starting Fastboot protocol support."
help?
Lcsglvr said:
hmmm... I'm in fastboot supposedly and tried to flash boot.img but it seems to be stuck at <waiting for device>
This happen to anyone else?
After search seems like a driver issue, but I have installed the drivers... I was previous rooted, so I know I have the drivers. Just to be sure, I ran the MotoHelper again. I don't understand. It's just seeing my device on the "Starting Fastboot protocol support."
help?
Click to expand...
Click to collapse
Yes. How did I fix it? I returned the xoom and had a new one two days later.
If the screen says something like "Entering RSD 2" then you're boned. The xoom won't be recognized in either the current state or in fastboot state by the computer, so no amount of commands will help. Even having the stock images doesn't help with that. Even RSDLite can't see the xoom in that state.
There have been several reports of people just being honest to Motorola and them fixing the device under the warranty.
Hmm honesty. I'll give it a shot.
Sent from my ADR6300 using XDA App
Is the final OEM lock necessary? It's quite a pain as your userdata gets wiped if you unlock it...
I was stuck on bootloop, with unrecognised device, through adb was able to get back into clockwork recovery somehow at first boot, think twice down volume? Could be wrong.
I was able tto rreflash zip 3.1 over thet top again.
sry if this is different and unhelpful, bu imagine things are pretty desperate if you are considering returning the device
zerin said:
Yes. How did I fix it? I returned the xoom and had a new one two days later.
If the screen says something like "Entering RSD 2" then you're boned. The xoom won't be recognized in either the current state or in fastboot state by the computer, so no amount of commands will help. Even having the stock images doesn't help with that. Even RSDLite can't see the xoom in that state.
There have been several reports of people just being honest to Motorola and them fixing the device under the warranty.
Click to expand...
Click to collapse
You're not boned at all. I had that happen to me so I just got back into fastboot, downloaded the files in the OP put ADB, Fastboot and the adb extensions into the file I downloaded then ran the commands and got me XOOM back up and running fine.
jbartcaps said:
You're not boned at all. I had that happen to me so I just got back into fastboot, downloaded the files in the OP put ADB, Fastboot and the adb extensions into the file I downloaded then ran the commands and got me XOOM back up and running fine.
Click to expand...
Click to collapse
You were likely in RSD 3, which is recognized by the computer. RSD 2 means adb and fastboot cannot see the device at all, so no flashing images is possible.
There's several states that all look very similar. Because some success was had with one doesn't mean it works for all. Motorola recognizes and is telling users that, in this state, the device needs to be sent back to them.
Can someone help us wifi xoom. Im stuck on the motorola screen and have a lil experience. I can fast boot reboot/fastboot device and it work but cant get the files from the hwi69 to fastboot on to it. I think im entering the commands wrong. Any advice would be appreciated
TheRedDroid said:
Hiya,
After dealing with a half-bricked Xoom, I did some research on this problem and found a solution.
If in any case, you happen to get stuck on the "Motorola Dual-Core Technology"
Solution to this (For the MZ604, One-Click rooted):
MZ604 Stock .imgs Download: http://developer.motorola.com/products/software/
*Make sure you have fastboot in the same directory as your adb for easy access*
1. Plug in your USB cord
2. Turn off your Xoom (Vol-Up + Power)
3. Boot into fastboot (Vol-Down + Power)
4. On your computer, open up a command prompt, and type the following:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
-or-
Code:
fastboot flash boot <path to boot.img>
fastboot flash system <path to system.img>
fastboot flash recovery <path torecovery.img>
fastboot flash userdata <path userdata.img>
fastboot erase cache
fastboot oem lock
5. Reboot the Xoom
Code:
fastboot reboot
6. There you go, back to stock!
Click to expand...
Click to collapse
Very good info to get into fastboot protocol:
Much thanks for the info. Worked like a champ. On an updated 3.2.1 XOOM I did an unlock, re-locked the wrong way, soft bricked, unbricked back to locked state. Finally followed your steps applied stock files and XOOM is re-locked and stock rocking back at 3.01. I needed to do all this to make sure I could get it back to stock in case it goes back to BB in 2 weeks. I was lucky enough to find one at a BB just not sure if I'll keep it. I plan on trying out some roms plus I heard Motorola is planning on doing an ICS push to the XOOM. ICS is very nice. It runs great on my unlocked Verizon G-Nex.. Again Thanks..
This post not only saved my half-bricked non-rooted Xoom, but also let me flash it from the Singapore firmware (bought if from Amazon, don't ask lol) to the regular USA firmware so that I can properly root it!
Thank you so very much!!
I've looked through other posts about this and nothing seems to help. I went to actually UNroot my Xoom so I can install the latest update because I had no use for a root, but when I went to do fastboot flash system system.img with the stock .img file, it takes forever then gives me an error... I don't know how to get past this. I just want my Xoom back to normal, even if I can get it back to a rooted normal I can live with that.
(Also, the first first time I tried unrooting, I realized I used the wrong device files. I used the Verizon ones, when I only have WiFi.)
Somebody please help me, or I feel like I have an expensive paperweight.
Also, whenever I go to restart, I'm stuck at the boot logo screen and no matter which boot.img I flash, it won't go past it.
hocplyr98 said:
I've looked through other posts about this and nothing seems to help. I went to actually UNroot my Xoom so I can install the latest update because I had no use for a root, but when I went to do fastboot flash system system.img with the stock .img file, it takes forever then gives me an error... I don't know how to get past this. I just want my Xoom back to normal, even if I can get it back to a rooted normal I can live with that.
(Also, the first first time I tried unrooting, I realized I used the wrong device files. I used the Verizon ones, when I only have WiFi.)
Somebody please help me, or I feel like I have an expensive paperweight.
Also, whenever I go to restart, I'm stuck at the boot logo screen and no matter which boot.img I flash, it won't go past it.
Click to expand...
Click to collapse
Did you have ClockworkMod recovery installed? If so, do you know how to boot into CWM recovery? Disconnect from thr computer if connected, and press power and volume up to hard reboot and when you get to the dual core image, wait about three seconds, then press volume down and you should see android recovery in upper left corner, then press volume up and press power to select it.
I'm suggesting this in the hope that you did a nandroid backup before you decided to mess around and that you could somehow still access it.
If not, do you now have the correct system image files in your platforms or tools folder in order to flash from fastboot? Can you get to the "starting fastboot protocol?"
Look for your correct 3.2 wifi images here:
http://forum.xda-developers.com/showthread.php?t=1080963
Commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Good luck!
okantomi said:
Can you get to the "starting fastboot protocol" screen?
Click to expand...
Click to collapse
yes if you somehow get into fast boot your problems can be solved.
I do not know whether by pressing vol up at boot time you can go to fastboot protocol screen.
okantomi said:
Did you have ClockworkMod recovery installed? If so, do you know how to boot into CWM recovery? Disconnect from thr computer if connected, and press power and volume up to hard reboot and when you get to the dual core image, wait about three seconds, then press volume down and you should see android recovery in upper left corner, then press volume up and press power to select it.
I'm suggesting this in the hope that you did a nandroid backup before you decided to mess around and that you could somehow still access it.
If not, do you now have the correct system image files in your platforms or tools folder in order to flash from fastboot? Can you get to the "starting fastboot protocol?"
Look for your correct 3.2 wifi images here:
http://forum.xda-developers.com/showthread.php?t=1080963
Commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Good luck!
Click to expand...
Click to collapse
Not sure if I have CWM installed, but I can access fastboot and that's not really helping. I'll try again with the link you provided, but I'm able to flash everything BUT system.img. I'll try again and get back to you.
UPDATE: Yeah... It's doing the exact same thing. It's stuck at fastboot flash system system.img. It just says that it's sending it and it takes a long time before an error message pops up saying that there are too many links.
UPDATE UPDATE: Okay, now, even in fastboot, it doesn't let me flash boot.img. I don't know what to do anymore
hocplyr98 said:
Not sure if I have CWM installed, but I can access fastboot and that's not really helping. I'll try again with the link you provided, but I'm able to flash everything BUT system.img. I'll try again and get back to you.
UPDATE: Yeah... It's doing the exact same thing. It's stuck at fastboot flash system system.img. It just says that it's sending it and it takes a long time before an error message pops up saying that there are too many links.
UPDATE UPDATE: Okay, now, even in fastboot, it doesn't let me flash boot.img. I don't know what to do anymore
Click to expand...
Click to collapse
This is where you need to talk to the experts. Go to #xoom at freenode.net and get some assistance.
okantomi said:
This is where you need to talk to the experts. Go to #xoom at freenode.net and get some assistance.
Click to expand...
Click to collapse
Not very much help from the "experts" there. I was completely ignored, and nobody responded to me...
hocplyr98 said:
Not very much help from the "experts" there. I was completely ignored, and nobody responded to me...
Click to expand...
Click to collapse
It's impossible to brick a Xoom. You can make or buy a factory cable and flash stock images from Motorola and follow up with OTA upgrades or flash whatever custom stuff you desire. The below links should save your Xoom. Don't forget to hit the thanks button
http://forum.xda-developers.com/showthread.php?t=1077414
http://developer.motorola.com/products/software/?pubid=987654
http://forum.xda-developers.com/showthread.php?t=1108518
Although if you're going to give up and aren't comfortable to continue working with it I would be very interested in purchasing it, you can PM me if interested.
Saintfyre said:
Although if you're going to give up and aren't comfortable to continue working with it I would be very interested in purchasing it, you can PM me if interested.
Click to expand...
Click to collapse
Keep an eye out on ebay, I just got a xoom on there with launcher force closing repeatedly for $264
Sent from my ADR6400L using XDA App
davidsos said:
It's impossible to brick a Xoom. You can make or buy a factory cable and flash stock images from Motorola and follow up with OTA upgrades or flash whatever custom stuff you desire. The below links should save your Xoom. Don't forget to hit the thanks button
http://forum.xda-developers.com/showthread.php?t=1077414
http://developer.motorola.com/products/software/?pubid=987654
http://forum.xda-developers.com/showthread.php?t=1108518
Click to expand...
Click to collapse
Not impossible but not as likely as you would think with the 100 "I think I bricked My xoom threads floating around.
To the OP...if you do not even know whether clockwork modified recovery is installed on your device then I am not sure you have the knowledge necessary to be messing with your device...I guess most people need to learn the hard way...
Hi all,
Been given a Nexus S i9023 by my brother who has been "tampering" with it and now it seems a bit messed up.
When booting up - it gets stuck on the "Google" screen with a padlock on it... I can get into fastboot and I can flash recovery but when I attempt to load any recovery - I get that same Google screen with the padlock! I've downloaded a stock rom and even flashed system etc via fastboot but that still gets me nowhere past the damn padlock!!
I've tried to "fastboot boot recovery.img" and I still get the Google screen with the padlock but it says "Fastboot status - OK" on the bottom left.
I've searched and searched but everyone just seems to give tips on how to flash recovery. I know how to flash recovery; it just seem to be going into it though! Could the internal memory be screwed?
Thanks for any advice!
Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot
albundy2010 said:
Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot
Click to expand...
Click to collapse
The phone stops at Google with the padlock on boot! Can't even get into the OS. Going to try to unbrick it and Odin but left my ubuntu laptop at my parents and can't be bothered to go get it... couldn't get it to work booting off cd rom. Kept giving me the "SBL Injection Failure Failed to find device" error booting ubuntu on a CD!
You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.
albundy2010 said:
You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.
Click to expand...
Click to collapse
No idea why I said Odin - I meant the unbrickable recovery thing.
I tried Odin with a Jig last night; got it into download mode and flashed with odin. Got the same result.
fastboot -w also gives the same issue...
If I have a storage issue - is there any way I can tell?
Basically you can tell by the issues you're having. Doing all the proper stuff to flash images etc and still having a booting/working device.
As far as a actual diagnostic tool I don't know of one. But it sure sounds like a hw issue to me.
I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance
Pironi90 said:
I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance
Click to expand...
Click to collapse
Reflash your recovery using fastboot.
polobunny said:
Reflash your recovery using fastboot.
Click to expand...
Click to collapse
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s
Pironi90 said:
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s
Click to expand...
Click to collapse
Flash custom recovery.img part
http://wiki.cyanogenmod.org/wiki/fastboot#Flash_Custom_Recovery.img
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?
polobunny said:
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
I think so yes, I could access recovery before if that's what you mean by unlocked
Pironi90 said:
I think so yes, I could access recovery before if that's what you mean by unlocked
Click to expand...
Click to collapse
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.
You are entering recovery. Stock recovery
If you want a custom one either flash with fastboot or if you're rooted with a app. Goo manager. Rom manager etc.
Keep it mind that if you're on a stock ROM the custom recovery gets overwritten back to stock when the phone boots up the os
Q
UselessSniper001 said:
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.
Click to expand...
Click to collapse
Then my phone is unlocked yes
polobunny said:
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
In installed the drivers and I installed the fastboot executable, but what do I have to do next? If I run the fastboot.exe, it just quickly shows a CMD-window and then disappears.
Edit:
I just discovered that, when I'm at the bootloader (I think it's called that way, the screen where you can select recovery), and I choose to reboot, I get the same 'error' as when I try to enter recovery.
Edit:
Alright, I was able to flash a new recovery, using cmd, but now when I try to enter my recovery, the phone gets stuck at a black screen with Google logo and padlock...
I have same problem as wolverine_2k who made the post. My nexus, can't start, I tried reboot and recovery but didn't work. After reboot or recovery I see Google logo, than Nexus screen and that is it. It didn't move to home screen and it stay with lighting screen all the time till I remove the battery. I can't power off it and don't know what to do. I can't transfer data with my PC (it don't recognize the device - only notice that "unknown device" is connected). Please any ideas?
P.S.: My English is not good, if someone answer do it simple please
Thanks!
So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.
fallnSaint said:
So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.
Click to expand...
Click to collapse
Mine did that for a short while after I screwed up a flash, I reflashed boot and while running tossed the adb command to get into fastboot and then left it properly. Haven't seen it since.
KitsunePaws said:
Mine did that for a short while after I screwed up a flash, I reflashed boot and while running tossed the adb command to get into fastboot and then left it properly. Haven't seen it since.
Click to expand...
Click to collapse
To clarify... Flash boot from recovery, while that is running adb reboot bootloader? If that is the case I have a different set of problems to "boot", I can't get my pc to recognize the phone while in recovery. Everything else is recognized, even reinstalled drivers to be certain, pc doesn't even try to install a driver for recovery. Tried both TWRP & CWM.
fallnSaint said:
To clarify... Flash boot from recovery, while that is running adb reboot bootloader? If that is the case I have a different set of problems to "boot", I can't get my pc to recognize the phone while in recovery. Everything else is recognized, even reinstalled drivers to be certain, pc doesn't even try to install a driver for recovery. Tried both TWRP & CWM.
Click to expand...
Click to collapse
Memory is fuzzy but I'm pretty sure I did it from fastboot, this happened to me about the time shabby was trying to fastboot boot boot.img and I ended up flashing it instead.
KitsunePaws said:
Memory is fuzzy but I'm pretty sure I did it from fastboot, this happened to me about the time shabby was trying to fastboot boot boot.img and I ended up flashing it instead.
Click to expand...
Click to collapse
I had this same issue when porting TWRP ^^^.
I can't seem to find my posts on it right now, but someone just said do a clean flash. No problems since
how did you do this please!
fallnSaint said:
So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.
Click to expand...
Click to collapse
Okay, this will probably help you...while your device is in Sticky Bit Factory Fastboot, open up a command prompt and connect to your device (given you know how to do so in your folder containing your fastboot app and drivers). Then type "fastboot oem fb_mode_clear" This command will allow your device to boot into system normally. Problem is (I think) when a failed flash occurs sometimes it sets your device in that mode and the above command clears it. Another way to manually place a device in the same state you described is to enter this command using fastboot: fastboot oem fb_mode_set. I believe that is how RSD Lite automatically reboots your device into factory fastboot mode after flashing partitions (.mbn) on your system so that it may resume flashing the boot, recovery, and system images, etc. Let me know if it helps.....
Sent from my XT897 using xda premium
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...