Related
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!
I am a noob to this.
I unlocked the bootloader and installed TWRP v2.5.0.0 to my One S T-Mobile.
The problem, I got is my phone is lock to the TWRF screen. I have been trying for several hours to get my phone to work again.
Could someone direct me how to get out of that screen?
I cannot load anything to the phone. Every time, I reboot it always end up with the TWRP screen.
get into bootloader and flash recovery again.
you could try the newer version (this is for the S4 variant not S3)
http://techerrata.com/browse/twrp2/ville
or Clockwork Mod recovery
http://www.clockworkmod.com/rommanager
Hold volume down and press the power button to get into bootloader
http://forum.xda-developers.com/showthread.php?t=1583427
grandlan said:
I am a noob to this.
I unlocked the bootloader and installed TWRP v2.5.0.0 to my One S T-Mobile.
The problem, I got is my phone is lock to the TWRF screen. I have been trying for several hours to get my phone to work again.
Could someone direct me how to get out of that screen?
I cannot load anything to the phone. Every time, I reboot it always end up with the TWRP screen.
Click to expand...
Click to collapse
Flash 2.3.3, its much more reliable.
2.4, 2.5 was buggy AFAIK.
tivofool said:
get into bootloader and flash recovery again.
you could try the newer version (this is for the S4 variant not S3)
http://techerrata.com/browse/twrp2/ville
or Clockwork Mod recovery
http://www.clockworkmod.com/rommanager
Hold volume down and press the power button to get into bootloader
http://forum.xda-developers.com/showthread.php?t=1583427
Click to expand...
Click to collapse
I loaded clockwork 6.0.3.1 and now the phone is lock to clockwork screen.
hmmm. So this "recovery bootloop" is still there.
Well if it were me I would run a RUU.exe for my device. Which would bring it back to stock and start over. quick and easy.
http://forum.xda-developers.com/showthread.php?t=2200930
lock your bootloader and run the ruu.exe while your phone is in fastboot usb
open a command terminal on your pc in the fastboot folder (shift + right click, select open command terminal)
fastboot oem lock
all in one toolkit can be used here instead
http://forum.xda-developers.com/showthread.php?t=1604677
tivofool said:
hmmm. So this "recovery bootloop" is still there.
Well if it were me I would run a RUU.exe for my device. Which would bring it back to stock and start over. quick and easy.
http://forum.xda-developers.com/showthread.php?t=2200930
lock your bootloader and run the ruu.exe while your phone is in fastboot usb
open a command terminal on your pc in the fastboot folder (shift + right click, select open command terminal)
fastboot oem lock
all in one toolkit can be used here instead
http://forum.xda-developers.com/showthread.php?t=1604677
Click to expand...
Click to collapse
The link for ruu you sent me is closed.
I down 2 from another website but they could not be loaded because of incompability.
I update the rom downloaded from HTC and still getting "error 155".
grandlan said:
The link for ruu you sent me is closed.
I down 2 from another website but they could not be loaded because of incompability.
I update the rom downloaded from HTC and still getting "error 155".
Click to expand...
Click to collapse
I have been able to flash the RUU from HTC after relocking the bootloader.
My phone has returned to stock and working again.
I'm glad you were able to fix it.
I had TWRP custom recovery installed, but I wanted to run an OTA update so I tried to flash back to stock recovery. My phone is now stuck in a reboot loop. It sits at a black screen with a small picture of an M8 and a red triangle and exclamation mark over it, then eventually it reboots. It boots to the white screen with the green "htc" logo, then goes back to the same black screen. I've tried holding down the power button, holding down Vol down+Power, holding down Vol up+Power, and holding down all three, but the reboot loop continues. Fastboot does not see my phone at any stage.
Here are the steps that I followed to arrive at where I am now:
1. Booted to Fastboot
2. Connected my phone to my PC
3. Opened a CMD prompt and accessed the fastboot directory
4. Ran this command: Fastboot oem rebootRUU
5. Ran this command: fastboot devices
6. Ensured that my phone was listed
7. Ran this command: fastboot flash recovery stock-recovery-4.4.3.img
8. Received a message stating that it was successful
9. Opened HBOOT on my phone
10. Opened Recovery on my phone
11. Phone went to a black screen with a small picture of a phone and a red triangle and exclamation mark
12. Phone stays there for a little while, then reboots to this screen, then the cycle starts over again
I did some searching but I couldn't find anything that helped. Anyone have any ideas?
Sorry, I mistakenly posted this in the wrong forum. Mods, could you please move this to Help & Troubleshooting?
UPDATE: I was able to get into fastboot by quickly holding down Vol Down + Power in between boot cycles, and fastboot is seeing my device on my PC. The problem now is that I don't know what to do from here.
craichead said:
UPDATE: I was able to get into fastboot by quickly holding down Vol Down + Power in between boot cycles, and fastboot is seeing my device on my PC. The problem now is that I don't know what to do from here.
Click to expand...
Click to collapse
What you are seeing is stock recovery. That is normal so relax.
What it sounds to me that you are wanting to do, is put your phone into a stock enough state in order to take any upcoming OTA correct?
I suggest at this point, that you take the latest available RUU (which has the latest OTA firmware included) which is also pre-rooted.
You will need to be able to get into Hboot however and you can do this by doing the following:
Hold Power+Volume up until the screen shuts off and goes black, then IMMEDIATELY hold power+volume down until you boot into hboot.
Once in hboot, you can always fastboot flash back TWRP to get your custom recovery back and flash custom roms.
I would do that first if there are things on your internal memory that you wish to save and off-load to your pc prior to taking the RUU.
If there is nothing you wish to save and you're ready to return to stock (but rooted so you can get back into the custom game later if you like), then follow the instructions outlined in the OP of this thread (which will provide a link for you to download the RUU needed): http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
If S=ON, select the S=ON link.
If S=OFF, select the S=OFF link.
Neo
Forum Moderator
ΠΣΘ said:
What you are seeing is stock recovery. That is normal so relax.
What it sounds to me that you are wanting to do, is put your phone into a stock enough state in order to take any upcoming OTA correct?
I suggest at this point, that you take the latest available RUU (which has the latest OTA firmware included) which is also pre-rooted.
You will need to be able to get into Hboot however and you can do this by doing the following:
Hold Power+Volume up until the screen shuts off and goes black, then IMMEDIATELY hold power+volume down until you boot into hboot.
Once in hboot, you can always fastboot flash back TWRP to get your custom recovery back and flash custom roms.
I would do that first if there are things on your internal memory that you wish to save and off-load to your pc prior to taking the RUU.
If there is nothing you wish to save and you're ready to return to stock (but rooted so you can get back into the custom game later if you like), then follow the instructions outlined in the OP of this thread (which will provide a link for you to download the RUU needed): http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
If S=ON, select the S=ON link.
If S=OFF, select the S=OFF link.
Neo
Forum Moderator
Click to expand...
Click to collapse
I actually don't think that it's in stock recovery. It still won't power on and is stuck in a reboot loop unless I hold Vol Down+Power during the reboot.
craichead said:
I actually don't think that it's in stock recovery. It still won't power on and is stuck in a reboot loop unless I hold Vol Down+Power during the reboot.
Click to expand...
Click to collapse
Hold down Volume UP+Power for about 10 seconds until the screen goes black and then immediately hold Volume Down+Power until you get into hboot.
ΠΣΘ said:
Hold down Volume UP+Power for about 10 seconds until the screen goes black and then immediately hold Volume Down+Power until you get into hboot.
Click to expand...
Click to collapse
I can get into HBOOT just fine, but no further. It's almost as if recovery isn't even installed.
craichead said:
I can get into HBOOT just fine, but no further. It's almost as if recovery isn't even installed.
Click to expand...
Click to collapse
You DO NOT NEED to flash stock recovery if you are wanting to return back to stock.
If there is nothing on your internal memory that you are wanting to save, then follow the instructions for flashing the RUU in hboot via rename and sdcard. I gave you the link you needed to follow which outlines precise directions to get you completely functional again in the phone state you desire.
ΠΣΘ said:
You DO NOT NEED to flash stock recovery if you are wanting to return back to stock.
If there is nothing on your internal memory that you are wanting to save, then follow the instructions for flashing the RUU in hboot via rename and sdcard. I gave you the link you needed to follow which outlines precise directions to get you completely functional again in the phone state you desire.
Click to expand...
Click to collapse
Everything I've read says that you do need to flash stock recovery in order to receive OTA updates, which is what I'm trying to do. I'm not trying to flash a zip.
craichead said:
Everything I've read says that you do need to flash stock recovery in order to receive OTA updates, which is what I'm trying to do. I'm not trying to flash a zip.
Click to expand...
Click to collapse
You need to be on stock firmware in order to take a OTA. That means stock firmware with FOTA enabled, and stock recovery.
Flashing a RUU returns you to a stock state of re-locked hboot, stock recovery, and stock rom with FOTA enabled. I can't help you any more if you don't follow the directions sir.
Flash the RUU and profit.
Good luck,
Neo
Flashing the RUU will flash the stock recovery.
Sent from my HTC6535LVW using Tapatalk
ΠΣΘ said:
You need to be on stock firmware in order to take a OTA. That means stock firmware with FOTA enabled, and stock recovery.
Flashing a RUU returns you to a stock state of re-locked hboot, stock recovery, and stock rom with FOTA enabled. I can't help you any more if you don't follow the directions sir.
Flash the RUU and profit.
Good luck,
Neo
Click to expand...
Click to collapse
I appreciate your help, but this isn't about me not following directions. I'm trying to figure out why my stock recovery doesn't seem to be flashing properly and, no disrespect intended, but you haven't addressed that issue directly.
craichead said:
I appreciate your help, but this isn't about me not following directions. I'm trying to figure out why my stock recovery doesn't seem to be flashing properly and, no disrespect intended, but you haven't addressed that issue directly.
Click to expand...
Click to collapse
None taken. I have not addressed the failed recovery flash because it could be a number of different reasons. I don't dwell on why things don't/didn't work.. I focus on the primary objective. Your primary objective was outlined in the OP of this thread and is as follows:
craichead said:
I wanted to run an OTA update
Click to expand...
Click to collapse
If the rom currently on your phone is in a completely stock state and simply rooted with no system files deleted or modified, then what you attempted to do with simply flashing a stock recovery would have been the minimally required thing to do.
If however you've deleted system files or flashed to a custom rom, then you will need to return your device to a stock rom, with fota enabled, and stock recovery flashed. The easiest method to achieve this directive is to flash a RUU, which contains all of the above requirements for being in a state to receive any OTA on top of updating all of your firmware to the latest OTA that we've received to date.
I do see your point, and loading the RUU might well work. But I would prefer to be able to back up my apps beforehand and I can't do that if I can't boot up. I did successfully re-flash TWRP recovery, but for some reason it still won't boot up; it's stuck in the reboot loop that I described (though I am still able to get into HBOOT).
craichead said:
I do see your point, and loading the RUU might well work. But I would prefer to be able to back up my apps beforehand and I can't do that if I can't boot up. I did successfully re-flash TWRP recovery, but for some reason it still won't boot up; it's stuck in the reboot loop that I described (though I am still able to get into HBOOT).
Click to expand...
Click to collapse
Dirty flash (without wiping) the rom you are currently on. If S=ON, fastboot flash the included boot.img with it as well.
ΠΣΘ said:
Dirty flash (without wiping) the rom you are currently on. If S=ON, fastboot flash the included boot.img with it as well.
Click to expand...
Click to collapse
Does that mean just restoring my backup in TWRP? I am S-OFF.
craichead said:
Does that mean just restoring my backup in TWRP? I am S-OFF.
Click to expand...
Click to collapse
That should work also, yes.
ΠΣΘ said:
That should work also, yes.
Click to expand...
Click to collapse
That worked! Thank you. I have all of my apps and they're all organized the way that I had them. I'm guessing the next thing I need to do is do a back-up, then flash the RUU, then the OTA should work?
craichead said:
That worked! Thank you. I have all of my apps and they're all organized the way that I had them. I'm guessing the next thing I need to do is do a back-up, then flash the RUU, then the OTA should work?
Click to expand...
Click to collapse
Yes. However, if you flash the latest RUU, you won't receive any OTA because the latest RUU contains all the firmware from our most recent OTA lol. You will be in a state though to receive any future OTAs should they come.
Make sure to back up your internal memory to either your sd card or your computer as the internal memory gets wiped in a RUU.
So I downloaded the RUU, but I can't seem to be able to copy the file to the external SD card as instructed. I go into ES File Explorer and access Device\storage\ext_sd and try to paste it there, but it says "not enough space". Which is weird, because it says that the directory is empty (and hidden files are enabled).
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 was trying to install a ROM and things got a bit messed up. I wiped system/cache/dalvik/data via TWRP. I then went to install the ROM but it failed due to only supporting hhz12h bootloader.
So now I'm kind of stuck. I can't update the bootloader because fastboot/ADB won't list the device in TWRP. Is there any way to launch an ADB server in TWRP so I can fastboot the bootloader? Doesn't look like there is.
If there's not:
Is there a TWRP zip-install hhz12h bootloader I can use? Looked around, couldn't find one.
If not I'll have to try and find/flash the original image..but fastboot is not going to happen so I have to find a zip installable one that'll work with hhz12d bootloader...which hopefully is around. Otherwise I could install literally anything just to get an ADB server so I can fastboot the hhz12h bootloader in there. Stupid problem to have right here, lol.
Any thoughts/help is appreciated. TIA.
Okay, so I got around the issue. I'm not sure if TWRP is supposed to be able to fastboot or ADB but mine would not, I was under the impression that I could fastboot or ADB in recovery. Maybe that was just a mistake on my part thinking that.
My workaround:
- Reboot into the bootloader (not TWRP recovery), 3 finger reset, power off, then power button + vol up + vol down until you get the OEM Android bootloader screen (unplug if plugged in, it didn't seem to want to go into bootloader when it was plugged in - maybe I just didn't wait long enough, but unplug if it doesn't want to go into the bootloader).
- From here I was able to fastboot, "fastboot devices" listed it
- I then flashed the bootloader: "fastboot flash bootloader bootloader-hammerhead-hhz12h.img" (may differ if you wan to flash different bootloader)
- I then rebooted into bootloader: "fastboot reboot-bootloader"
- I then flashed recovery: "fastboot flash recovery openrecovery-twrp-2.8.5.2-hammerhead.img" (may differ for different version of recovery)
- I then used vol up/vol down to select "reboot recovery", and hit the power button
- TWRP booted and from there, now that I have the hhz12h.img bootloader flashed I could install the ROM, so I wiped data/dalvik/cache/system again, installed the ROM, installed Gapps, and rebooted, good to go.
FYI ADB works into recovery mode (TWRP) and Android. Fastboot can only be used when you are in the bootloader.
You did the right thing except that it wasn't necessary to flash TWRP. Flashing a bootloader.img only erases the boot partition so the recovery isn't concerned.
Primokorn said:
FYI ADB works into recovery mode (TWRP) and Android. Fastboot can only be used when you are in the bootloader.
You did the right thing except that it wasn't necessary to flash TWRP. Flashing a bootloader.img only erases the boot partition so the recovery isn't concerned.
Click to expand...
Click to collapse
Got it. For whatever reason I could not get ADB to see the device while I was in TWRP. I tried the ADB sideload feature in 'advanced' but it just waited and waited and waited forever. I believe ADB is set up properly on my system because it works fine on ROM. Not sure what the deal is with that, but I don't have much reason to go into ADB in recovery anyway aside from this issue, so it's [hopefully] not a big deal.
As for flashing the recovery, yeah, bad habit I guess. On my old phone (Fascinate Galaxy S 1), if you had custom recovery and had to 3-finger reset to bootloader because your phone wouldn't turn on or was bootlooping or whatever the recovery was boned, had to re-odin flash it. So it's stuck in my memory now that if I had to 3 finger it I better flash recovery. I'll try to knock myself out of that habit .
Thanks!
Syndacate said:
Is there a TWRP zip-install hhz12h bootloader I can use?
Click to expand...
Click to collapse
This one works.
http://forum.xda-developers.com/showpost.php?p=60879785&postcount=1246
EDIT - Looks like the poster took it down. I'll upload and get back to you.
EDIT part deux - http://d-h.st/zEex (includes the last modem)
Also that's a really old version of twrp you flashed...
Sent from my Nexus 5 using Tapatalk
Wakamatsu said:
This one works.
http://forum.xda-developers.com/showpost.php?p=60879785&postcount=1246
EDIT - Looks like the poster took it down. I'll upload and get back to you.
EDIT part deux - http://d-h.st/zEex (includes the last modem)
Click to expand...
Click to collapse
Thanks, I'll snag that just in case I ever have a fastboot outage or I'm on a system w/o ADB/fastboot or something.
ldubs said:
Also that's a really old version of twrp you flashed...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Haha, I didn't even look at the dates, I just went to the "Tools/Utilities" page for the Nexus 5 and it was the top link....I didn't think too much on it, just figured top link = most recent = latest.
http://forum.xda-developers.com/showthread.php?t=2511507
I'll dig around for a thread which has latest and flash that on there, can't expect old versions to work flawlessly, now can we?
EDIT:
That actually might have just been a copy/paste error on my part, as I had the old TWRP lying around for fastboot and copy/pasted the name from that. I used TWRP (ROOT) app to install and I chose latest (or so I thought). Now I have literally NO idea which one I was using -_-.
No worries glad you got it sorted. You can flash an image file in twrp now BTW.
Sent from my Nexus 5 using Tapatalk