Huawei Mate S bricked!! Please help!! - Huawei Mate S

Hello, i wanted to install TWRP but it doesnt work. After that i got only the Huawei Logo. After that i try to repair it with pathcing new BOOT, SYSTEM and RECOVERY Files via Fastboot. The Files are from the Stock-Rom.
I just get the Recovery Menu after i pluged it in with USB. But every patch is useless. Power/- or Power/+ doesnt work, only Huawei Logo pops up? Is this a Hardbrick? Sorry for my English i hope its understandable.

Blizz' said:
Hello, i wanted to install TWRP but it doesnt work. After that i got only the Huawei Logo. After that i try to repair it with pathcing new BOOT, SYSTEM and RECOVERY Files via Fastboot. The Files are from the Stock-Rom.
I just get the Recovery Menu after i pluged it in with USB. But every patch is useless. Power/- or Power/+ doesnt work, only Huawei Logo pops up? Is this a Hardbrick? Sorry for my English i hope its understandable.
Click to expand...
Click to collapse
what exactly did you do?
how did you "install twrp"?
how did you "patch" new boot, system, recovery?

Tuerkay said:
what exactly did you do?
how did you "install twrp"?
how did you "patch" new boot, system, recovery?
Click to expand...
Click to collapse
i flashed it with the command "fastboot flash recovery twrp-2.8.7.0-carrera.img"
after this i got no recovery system because it dont works.
After some trys to patch it again i maked my mate s unusable.
I tryed to repair my mate s with
"fastboot flash recovery", "fastboot flash boot", and "fastboot flash system"
(i flashed a factory rom, so without updates)
At now, i only get in the download mode. im unable to update the system via micro-sd.

Hi, it happend to me too yesterday. I solved it by reinstalling stock recovery (same way you installed twrp) and a stock rom. And at the end, it runs again.
The procedure did not work flawless. E.g. during installing of stock rom (B321) it got stuck at 90%, I had to repeat it again and again.
So good luck.

Blizz' said:
i flashed it with the command "fastboot flash recovery twrp-2.8.7.0-carrera.img"
after this i got no recovery system because it dont works.
After some trys to patch it again i maked my mate s unusable.
I tryed to repair my mate s with
"fastboot flash recovery", "fastboot flash boot", and "fastboot flash system"
(i flashed a factory rom, so without updates)
At now, i only get in the download mode. im unable to update the system via micro-sd.
Click to expand...
Click to collapse
Fastboot flash recovery and the path (i think you must flash recovery2.IMG too)
Fastboot flash Boot.IMG and the path
Fastboot flash system.IMG and the path
You can flash userdata cache and cust too
---------- Post added at 11:34 PM ---------- Previous post was at 11:31 PM ----------
I dont think the mate s have a download mode.......it has only bootloader and recovery menue

Related

Please Help! Fastboot not flashing Recovery

I apologize in advance if this has been answered already.
Before you ask:
My bootloader is unlocked
My phone is bricked due to an update that caused processes and apps to crash and make the factory reset on stock recovery useless so I tried to downgrade from lollipop to kitkat. My aim is to see if a custom recovery will format the phone properly so that flashing the stock firmware works. I think it isn't working because my userdata and cache partitions may be corrupted or something because this is what I get when I try factory reset on stock recovery:
E: blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata failed and E: blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/cache failed.
I am thinking that I need a custom recovery but when I flash one and try and boot into recovery I end up with the stock recovery and no errors are given during the flash and the pink text that says "mismatched partition size" doesn't show up. When I run "fastboot erase all" it completes with no errors but doesn't seem to do anything so could fastboot be at fault? When I try booting it with "fastboot boot recovery.img" all i get is the Motorola logo flickering every second or so. Unless I can fix my phone without a custom recovery, I need help!!!
If any more information is needed I will try to provide but am somewhat of a noob. All responses are appreciated. Thanks
You need mfastboot to flash a stock firmware
fburgos said:
You need mfastboot to flash a stock firmware
Click to expand...
Click to collapse
Whats the difference between fastboot and mfastboot?
fburgos said:
You need mfastboot to flash a stock firmware
Click to expand...
Click to collapse
I have been using mfastboot for both the firmware flash and for the custom recovery flash
I am having the same issue as well. I flash a custom recovery ... it says it flashes ok but I cannot enter recovery.
I too was getting the blinking Motorola logo. Had to power off and then turn back on to get the phone to boot up. I cannot relock my bootloader either !
This all happened when I returned to stock to get the official lollipop update. I was able to flash gpt.bin before that and flash recovery and everything but since I did the update I can't do much of anything.
I tried loading twrp just to get into it. That did work once but I don't know how it did it. I was able to do a backup and flash a custom rom but still can't get into twrp. I've tried fastboot and mfastboot many times over and still it says flash ok but I cannot enter twrp or any custom recovery.
---------- Post added at 03:20 PM ---------- Previous post was at 03:17 PM ----------
I am thinking that I either need to flash an earlier version of twrp besides the 2860 that I'm trying to flash or relock then unlock the bootloader again, if I can. Not sure at this point but I'm going to continue to research and try something else.
rogerrylez said:
I am having the same issue as well. I flash a custom recovery ... it says it flashes ok but I cannot enter recovery.
I too was getting the blinking Motorola logo. Had to power off and then turn back on to get the phone to boot up. I cannot relock my bootloader either !
This all happened when I returned to stock to get the official lollipop update. I was able to flash gpt.bin before that and flash recovery and everything but since I did the update I can't do much of anything.
I tried loading twrp just to get into it. That did work once but I don't know how it did it. I was able to do a backup and flash a custom rom but still can't get into twrp. I've tried fastboot and mfastboot many times over and still it says flash ok but I cannot enter twrp or any custom recovery.
---------- Post added at 03:20 PM ---------- Previous post was at 03:17 PM ----------
I am thinking that I either need to flash an earlier version of twrp besides the 2860 that I'm trying to flash or relock then unlock the bootloader again, if I can. Not sure at this point but I'm going to continue to research and try something else.
Click to expand...
Click to collapse
Is it possible to put tempcwm.zip onto the internal memory so it can be booted through "apply update from sd card" as that is the next thing I'm going to try but don't know if it will be compatible. I tried to flash the lollipop firmware by xda member reefuge to see if that would do anything but it didn't. Perhaps it might work for you.
Quadron said:
Is it possible to put tempcwm.zip onto the internal memory so it can be booted through "apply update from sd card" as that is the next thing I'm going to try but don't know if it will be compatible. I tried to flash the lollipop firmware by xda member reefuge to see if that would do anything but it didn't. Perhaps it might work for you.
Click to expand...
Click to collapse
That's assuming you can get into any recovery !
I was able to "boot" into twrp using the Moto-G-2014-ToolKit. It appears to be rom related - "Quantum-OS. I just recently installed Candy5 and have no problems rebooting into recovery whether from the phone or from ADB command.

Flashing twrp on stock v20i

So I came from a stock lollipop Tmobile h811 non rooted
To stock MM v20i.
Ive tried flashing twrp 3.0 for cm13, and no matter what,
I get failed: (remote unknown command at the end after it sends recovery.
Its already unlocked(bootloader)
Thanks.
[email protected] said:
So I came from a stock lollipop Tmobile h811 non rooted
To stock MM v20i.
Ive tried flashing twrp 3.0 for cm13, and no matter what,
I get failed: (remote unknown command at the end after it sends recovery.
Its already unlocked(bootloader)
Thanks.
Click to expand...
Click to collapse
Type: fastboot boot (path goes here)
You can drag and drop the twrp img into the command window. This will ensure you have the correct path
[email protected] said:
So I came from a stock lollipop Tmobile h811 non rooted
To stock MM v20i.
Ive tried flashing twrp 3.0 for cm13, and no matter what,
I get failed: (remote unknown command at the end after it sends recovery.
Its already unlocked(bootloader)
Thanks.
Click to expand...
Click to collapse
Follow this instruction
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
mingkee said:
Follow this instruction
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Click to expand...
Click to collapse
That link doesn't really solve the OP's issue. I have the same issue. BUT - your link did show me that I can BOOT the .img file, I can't flash the .img file. I've verified the bootloader is unlocked by the fastboot getvar command.
I'm not sure what to do next. Installing OpenGapps causes a boot loop and the only thing I can do at this point is a factory reset with the OEM recovery since in the boot loop adb is unresponsive.
joesee said:
That link doesn't really solve the OP's issue. I have the same issue. BUT - your link did show me that I can BOOT the .img file, I can't flash the .img file. I've verified the bootloader is unlocked by the fastboot getvar command.
I'm not sure what to do next. Installing OpenGapps causes a boot loop and the only thing I can do at this point is a factory reset with the OEM recovery since in the boot loop adb is unresponsive.
Click to expand...
Click to collapse
The instruction shows how to flash recovery.img with TWRP though I have no clue how to do it.
I got that error the first time I did it, it was because of a misspelling of the command.
If you already unlocked the bootloader, while in fastboot, you only type "fastboot boot" + "path to twrp img on computer" OR instead of typing out the path, you may drag and drop the file into the command window.
Once it boots to twrp, flash twrp from within the booted img. That ensures you have permanent twrp.
If you were able to unlock your bootloader, the only thing stopping you from loading twrp is improper spelling and path to the img. Almost every error I have seen is from not following the directions.
Vseprz said:
If you already unlocked the bootloader, while in fastboot, you only type "fastboot boot" + "path to twrp img on computer" OR instead of typing out the path, you may drag and drop the file into the command window.
Once it boots to twrp, flash twrp from within the booted img. That ensures you have permanent twrp.
If you were able to unlock your bootloader, the only thing stopping you from loading twrp is improper spelling and path to the img. Almost every error I have seen is from not following the directions.
Click to expand...
Click to collapse
OK, just so I understand correctly, the proper sequence of events is to use fastboot to boot TWRP (which I can do) then, once in TWRP, I can then flash the twrp .zip file, right? Does anyone know if the LG's bootloader overwrites the recovery partition upon boot (in other words, do I have to boot straight to recovery after I flash to ensure it sticks?)
Sorry for the obtuse questions, I've got a lot of experience with Samsung flashing back in the KK and LP days, but not MM.
Thanks in advance!!
joesee said:
OK, just so I understand correctly, the proper sequence of events is to use fastboot to boot TWRP (which I can do) then, once in TWRP, I can then flash the twrp .zip file, right? Does anyone know if the LG's bootloader overwrites the recovery partition upon boot (in other words, do I have to boot straight to recovery after I flash to ensure it sticks?)
Sorry for the obtuse questions, I've got a lot of experience with Samsung flashing back in the KK and LP days, but not MM.
Thanks in advance!!
Click to expand...
Click to collapse
So you have flashed 20i which overwrites twrp with the stock recovery.
You then go through the steps for unlocking the boot loader.
After the boot loader is unlocked, you may boot into twrp with the fastboot boot command.
When that boots into twrp, flash twrp from within that to have it stick.
Have a question and maybe someone can help. Me getting carried away installed twrp from external partition. Now i cannot boot into recovery. Tried flashing using flashify and twrp manager. but flashify does not install after reboot and there is no option for h811 in twrp manager. Anyway to fix this?
Sent from my LG-H811 using Tapatalk
Vseprz said:
So you have flashed 20i which overwrites twrp with the stock recovery.
You then go through the steps for unlocking the boot loader.
After the boot loader is unlocked, you may boot into twrp with the fastboot boot command.
When that boots into twrp, flash twrp from within that to have it stick.
Click to expand...
Click to collapse
Yes, that's exactly the steps I do. I've flashed 20i. I used fastboot to boot into twrp. I then "install" the twrp zip file. Says it flashes with no issues. I then reboot the phone. Still has stock recovery.
I've confirmed my bootloader is unlocked with the fastboot getvar all. I've also tried all three versions of twrp available (.1, .2 and .3) and still doesn't work. Yet twrp works fine if I boot it.
joesee said:
Yes, that's exactly the steps I do. I've flashed 20i. I used fastboot to boot into twrp. I then "install" the twrp zip file. Says it flashes with no issues. I then reboot the phone. Still has stock recovery.
I've confirmed my bootloader is unlocked with the fastboot getvar all. I've also tried all three versions of twrp available (.1, .2 and .3) and still doesn't work. Yet twrp works fine if I boot it.
Click to expand...
Click to collapse
How did you confirm you have stock recovery? Did you use adb reboot recovery? Or did you use hardware keys to boot to it? Because if you use hardware keys you still get the initial confirm factory reset. You just have to accept then it boots to twrp.
---------- Post added at 10:44 AM ---------- Previous post was at 10:22 AM ----------
99problemz said:
Have a question and maybe someone can help. Me getting carried away installed twrp from external partition. Now i cannot boot into recovery. Tried flashing using flashify and twrp manager. but flashify does not install after reboot and there is no option for h811 in twrp manager. Anyway to fix this?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
If boot loader is unlocked you should load twrp from fastboot.
Vseprz said:
How did you confirm you have stock recovery? Did you use adb reboot recovery? Or did you use hardware keys to boot to it? Because if you use hardware keys you still get the initial confirm factory reset. You just have to accept then it boots to twrp.
---------- Post added at 10:44 AM ---------- Previous post was at 10:22 AM ----------
If boot loader is unlocked you should load twrp from fastboot.
Click to expand...
Click to collapse
Hahaha now that's funny!! I bet I've been through 50 blog posts on various sites to try to figure this out. Having successfully installed Viper I didn't want to take the chance and pass that confirm wipe factory question.
I feel like a complete tool. Seriously, thank you for taking the time to respond to me!
joesee said:
Hahaha now that's funny!! I bet I've been through 50 blog posts on various sites to try to figure this out. Having successfully installed Viper I didn't want to take the chance and pass that confirm wipe factory question.
I feel like a complete tool. Seriously, thank you for taking the time to respond to me!
Click to expand...
Click to collapse
I'm glad it all worked out! :good:
finding I have to re-flash with flashify each time
using twrp-2.8.7.1, I get only the first reboot from there with hardware keys letting me into twrp after accepting the first factory reset prompt and denying the second. After that cant do it again unless I re-flash. Same thing happens if I flash it from within twrp. Can use terminal, su, boot recovery and I am in., or ADB/fatsboot Primarily worried about a soft brick condition. H-811, v1 20i stock, unlocked bootloader and rooted. DE-bloated,
Any Ideas, Thanks
jdoebean said:
using twrp-2.8.7.1, I get only the first reboot from there with hardware keys letting me into twrp after accepting the first factory reset prompt and denying the second. After that cant do it again unless I re-flash. Same thing happens if I flash it from within twrp. Can use terminal, su, boot recovery and I am in., or ADB/fatsboot Primarily worried about a soft brick condition. H-811, v1 20i stock, unlocked bootloader and rooted. DE-bloated,
Any Ideas, Thanks
Click to expand...
Click to collapse
You drop the twrp file
In fastboot folder open command prompt and flash twrp first just rename it simply to recovery.img while in the fastboot folder
Type fastboot flash recovery recovery.img
Or just fastboot flash recovery.img
Then it should boot you into twrp
Once booting into twrp flash the supersu zip in your internal sd
Once you have root and reboot all you have to do is use flashify app and download twrp from the app and flash it Twrp sticks from there.
Sent from my LGMS631 using XDA Free mobile app

Can't access to TWRP anymore

Hello everyone,
so here is my configuration:
-latest TWRP (3.0.2) with F2S support
-bootloader unlocked
-the N6 is rooted
-ROM: AICP MM
2 days ago I tried to reboot to recovery to flash a more recent version of my AICP ROM. I just had the time to see the TWRP boot logo and then the phone rebooted to load the system. I can't access anymore to my recovery. I tried to rename the twrp directory on the internal SD but it does not change anything.
I reflashed TWRP with ADB and fastboot, but it didn't resolve the problem.
The only change I made recently was to flash a new radio to try to improve my connectivity.
I flashed 5.34 with the new bootloader in fastboot. Then I tried 5.32 without changing the bootloader and finally the 5.36 with the latest bootloader. So I don't know when the problem occured but now my phone even reboots randomly !
So if anyone has a solution you're welcome !
What happens when you connect the N6 to the PC and issue the fastboot boot recovery command?
Check your volume controls. They may be stuck.
Had this Problem on an other device . No recovery flash with fastboot . Dont no how , but Trwp manager APP from playstore did it .
you have to flash twrp right.. if you use a toolkit or flash the recovery with fastboot boot(instead of fastboot flash) then it will only boot into twrp 1 time, then you will need to flash it again if you want to use it again.
Strephon Alkhalikoi said:
What happens when you connect the N6 to the PC and issue the fastboot boot recovery command?
Check your volume controls. They may be stuck.
Click to expand...
Click to collapse
If I'm using "adb reboot recovery", the N6 is rebooting and load the recovery but I only see the TWRP boot logo. Then it's rebooting from the Google logo...
I've flashed the recovery with "fastboot flash recovery recovery.img", but I've also tried with flashify and still the same problem !
In fact I think that's a problem which is related to the upgrade of the bootloader or the radio. I'm with the 71.21 bootloader which came with the latest radio (from the Android N images). Even with the previous bootloader the problem occured. So until which bootloader can I downgrade without bricking my phone ?
Thanks in advance for your suggestions !
marcp39 said:
If I'm using "adb reboot recovery", the N6 is rebooting and load the recovery but I only see the TWRP boot logo. Then it's rebooting from the Google logo...
I've flashed the recovery with "fastboot flash recovery recovery.img", but I've also tried with flashify and still the same problem !
In fact I think that's a problem which is related to the upgrade of the bootloader or the radio. I'm with the 71.21 bootloader which came with the latest radio (from the Android N images). Even with the previous bootloader the problem occured. So until which bootloader can I downgrade without bricking my phone ?
Thanks in advance for your suggestions !
Click to expand...
Click to collapse
yea, you can downgrade, but why? and why are you doing adb reboot recovery? you know that you can use a terminal emulator app on your phone and then reboot recovery using it? every custom rom should also have a reboot recovery option when pressing the power button as well.
simms22 said:
yea, you can downgrade, but why? and why are you doing adb reboot recovery? you know that you can use a terminal emulator app on your phone and then reboot recovery using it? every custom rom should also have a reboot recovery option when pressing the power button as well.
Click to expand...
Click to collapse
I want to try to downgrade the bootloader because this problem occured just after changing it. I've not modified anything else.
I've tried with a terminal emulator, same symptoms.
If I'm using the reboot menu of AICP it's exactly the same behaviour. And that's the usual function I'm using to reboot to recovery. In fact all the commands are working, the N6 is rebooting to recovery but I just see the TWRP logo, then it reboots the phone to the google logo, then it starts the system...
Even if I'm launching recovery from the bootloader, I'm getting the same result.
marcp39 said:
I want to try to downgrade the bootloader because this problem occured just after changing it. I've not modified anything else.
I've tried with a terminal emulator, same symptoms.
If I'm using the reboot menu of AICP it's exactly the same behaviour. And that's the usual function I'm using to reboot to recovery. In fact all the commands are working, the N6 is rebooting to recovery but I just see the TWRP logo, then it reboots the phone to the google logo, then it starts the system...
Even if I'm launching recovery from the bootloader, I'm getting the same result.
Click to expand...
Click to collapse
sounds like you need to clear the recovery partition, then flash twrp again.
simms22 said:
sounds like you need to clear the recovery partition, then flash twrp again.
Click to expand...
Click to collapse
With "fastboot erase recovery" ?
marcp39 said:
With "fastboot erase recovery" ?
Click to expand...
Click to collapse
honestly, i dont remember how.
So here are my last attempts:
-I've tried to clean the cache with "fastboot erase cache", I thought it could be corrupted. BIG MISTAKE ! This time the phone is bootlooping when lauching the ROM...
And of course, I'm making some backups but they are on the "internal sd"... So I can't access my files anymore !
-I've also tried "fastboot erase recovery" and reflashed recovery. No improvement.
-I've downgraded the bootloader from 71.21 to 71.18. Nothing changed.
-I was asking myself if last time I didn't enter a wrong command in typing "fastboot flash boot bootloader.img" instead of "fastboot flash bootloader bootloader.img". So even if I've added benzocore on my AICP ROM, I decided to flash the boot.img from AICP zipfile on the boot partition (+ erase boot). So this time no more bootlooping of the ROM, because I'm stuck on the google logo :crying:...
I've never encounter such a desperate situation ! I don't even understand why I can't boot in recovery...
I could reflash a factory image on my phone, but this would erase all my datas !
Do you think I could reflash a factory image (except the data partition), just to be able to get a valid recovery, and access my files from the computer ? Then I could erase data partition, and reflash a new ROM ?
I don't want to precipitate the next actions because I don't have any joker... and with this stupid idea of not putting any µSD slot in most phones nowadays we're captive of the situation when the phone is bricked ! We can't recover data easily, even with adb pull (which does not work in my case of course).
So please share your ideas, they'll be welcome ! I've read A LOT of posts on XDA and others, but no solution until now....
TIBU to back up your data and then move the data on to PC. Use NRT WUG Fresh tool to flash MOB30M (stock, unroot) and then root/recovery and then start over. If you don't want encrypt then "format data" once in TWRP and then flash custom kernel like HellsCore to not force encrypt.
marcp39 said:
I could reflash a factory image on my phone, but this would erase all my datas !
Click to expand...
Click to collapse
Don't use FlashAll, it's usually broken, anyway. But rather unpack the zip, flash boot and system. And either flash cache or erase it. It does the same.
HueyT said:
TIBU to back up your data and then move the data on to PC. Use NRT WUG Fresh tool to flash MOB30M (stock, unroot) and then root/recovery and then start over. If you don't want encrypt then "format data" once in TWRP and then flash custom kernel like HellsCore to not force encrypt.
Click to expand...
Click to collapse
TIBU for Titanium Backup ? How do you want I use this app since I don't have access to android, only to the bootloader ? You want me to install MOB30M without wiping the datas from my current rom, export the result and then wipe everything to make a clean install ?
marcp39 said:
TIBU for Titanium Backup ? How do you want I use this app since I don't have access to android, only to the bootloader ? You want me to install MOB30M without wiping the datas from my current rom, export the result and then wipe everything to make a clean install ?
Click to expand...
Click to collapse
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------
HueyT said:
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
Click to expand...
Click to collapse
Just looked it up. You can't backup your data via fastboot but you can using "adb" command. The problem is getting "adb" to work requires "USB Debugging" to be on and android working Thus, you're likely stuck losing your data.
HueyT said:
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------
Just looked it up. You can't backup your data via fastboot but you can using "adb" command. The problem is getting "adb" to work requires "USB Debugging" to be on and android working Thus, you're likely stuck losing your data.
Click to expand...
Click to collapse
Yeah unfortunately we can do it with adb (like this http://stackoverflow.com/questions/8650407/how-to-copy-selected-files-from-android-with-adb-pull) but not with fastboot. Tomorrow I'll try to flash each *.img from MOB30M separately and see if I can recover a working recovery to access to my datas ! Thanks for your answer btw.
Hello everyone !
So here are the last news...
I've tried an older TWRP like 2.8.x.x same problem.
I've flashed all the *.img from MOB30M except data, but my recovery was still not accessible !!!
So I was resigned to format my data and flash the *.img on it.
This time it worked, my N6 was coming back to life !!! Then I had to root it, flash the recovery, remove encryption and format data with F2FS !
I still don't understand how a corrupted (?) data partition could block the running of recovery, that's strange !
So now I have to restore the data from a TWRP image dated 04-16 I had on my NAS...I can tell you that in the future I won't let my recent backups only on internal storage !
Will you believe me if I tell you that the same problem is occuring again :crying: ?
Several days ago, it started when the impossibility to enter the recovery but this time it does not reboot in bootloader, just stuck... Now I got random reboots and stange behaviour from applications !
I NEVER had a serious problem like that with my N6 before. So I don't understand how can I get data corruption like this ? Last time I was using Benzo kernel, now DeYuS kernel but with no exceptional settings, no overclocking.
I've just disabled "forceencrypt" and convert data to F2FS (no problem before).
So does anyone have a clue about this problem ?

Hard Brick L-19

Hello guys
Need your help or ideas
So i Hard Bricked my P9 i can only enter fastboot.
Phone was on Android N first build,flashed it with TWRP,but i dint have stock app likes camera calculator e.t.c
Phone was working OK but i whanted to get original camera.
So there was made TWRP for android N, i flashed it TWRP worked system was booting, but TWRP not mounting /data, so there was tuto for fix that.
Need to flash zip -> repair /data -> resize ( thats was begining of problem )
zip was success, but format and repair was with error 4
system not booting anymore stuck on bootloop, with twrp.
Tried re-flash N with TWRP dint helped . Only lost TWRP
So i flashed L19C432B136 with dload. update was success, but I don't know why system wast booting, there was no orginal recovery i can't enter it or update with dload.
Stuck in screen "Phone is unlocked and can't be trusted"
Flashing TWRP for MM or N is success but phone don't enter IT
Flashing stock recovery from B136 dint helped ( i tried stock recovery from B322 ; no success)
Tried flashing SYSTEM.img BOOT.img RECOVERY.img from 322, all is sucess but phone not skipping screen ( Phone is unlocked and can't be trusted )
Any idea how to get phone back from dead?
I can only enter fastboot.
Is i possible to flash something true fastboot?
I have full updates of L19C432B182 and L19C432B161.
richish said:
Hello guys
Need your help or ideas
So i Hard Bricked my P9 i can only enter fastboot.
Phone was on Android N first build,flashed it with TWRP,but i dint have stock app likes camera calculator e.t.c
Phone was working OK but i whanted to get original camera.
So there was made TWRP for android N, i flashed it TWRP worked system was booting, but TWRP not mounting /data, so there was tuto for fix that.
Need to flash zip -> repair /data -> resize ( thats was begining of problem )
zip was success, but format and repair was with error 4
system not booting anymore stuck on bootloop, with twrp.
Tried re-flash N with TWRP dint helped . Only lost TWRP
So i flashed L19C432B136 with dload. update was success, but I don't know why system wast booting, there was no orginal recovery i can't enter it or update with dload.
Stuck in screen "Phone is unlocked and can't be trusted"
Flashing TWRP for MM or N is success but phone don't enter IT
Flashing stock recovery from B136 dint helped ( i tried stock recovery from B322 ; no success)
Tried flashing SYSTEM.img BOOT.img RECOVERY.img from 322, all is sucess but phone not skipping screen ( Phone is unlocked and can't be trusted )
Any idea how to get phone back from dead?
I can only enter fastboot.
Is i possible to flash something true fastboot?
I have full updates of L19C432B182 and L19C432B161.
Click to expand...
Click to collapse
You have 2 choices with this.
If you can still boot into TWRP,
1. Flash the Beta Update.zip
2. Power off phone.
3. Press up button whilst powering up phone.
4. You will now be in stock recovery and you can perform a factory reset.
5. the device will now boot in to N beta but will be missing the vendor apps.
There is another way to fix if this doesn't work. Tell me if this method works first.
Edit: I just read in the op that you flashed the update and had stock recovery.
The reason it won't boot is because you need to have b322 flashed and you have to factory reset to repair the corrupt file system. To do this follow these instructions.
1. You need to flash the Boot, Recovery and System images from b322 in fastboot.
2. Then enter stock recovery (Vol + and Power)
3. Then factory reset (this is essential as it repairs the file system and enables boot)
4. The device will then boot.
5. (Optional )If you want to go back from the beta you have to flash the rollback.app to b300 through th dload method first then you can flash a Android 6.0 through the dload method.
Regards
Lee
thel2dab said:
You have 2 choices with this.
If you can still boot into TWRP,
1. Flash the Beta Update.zip
2. Power off phone.
3. Press up button whilst powering up phone.
4. You will now be in stock recovery and you can perform a factory reset.
5. the device will now boot in to N beta but will be missing the vendor apps.
There is another way to fix if this doesn't work. Tell me if this method works first.
Regards
Lee
Click to expand...
Click to collapse
Cant Enter TWRP
noone of recoverys work
richish said:
Cant Enter TWRP
noone of recoverys work
Click to expand...
Click to collapse
Edited my previous post with another method.
thel2dab said:
Edited my previous post with another method.
Click to expand...
Click to collapse
fast qestion
there is 2 recoverys, does both need to be flashed?
@richish
If you get really stuck I can teamviewer your pc and help.
Or you can facebook message me direct.
I had exactly the same issue when I first tried to flash the properdatafix with TWRP for N
Regards
---------- Post added at 10:26 PM ---------- Previous post was at 10:24 PM ----------
richish said:
fast qestion
there is 2 recoverys, does both need to be flashed?
Click to expand...
Click to collapse
You can flash both.
fastboot flash recovery recovery.img
fastboot flash recovery2 recovery2.img
I don't think it is essential but it won't hurt to do it anyway.
---------- Post added at 10:35 PM ---------- Previous post was at 10:26 PM ----------
[/COLOR @richish
I seen you PM. I am not sure it will wok by flashing B182. I think you have to flash B322 first.
Regards
fist you have to flash stock recovery from emui 5(android N) through fastboot.
second , download the rollback package,extract it and put it on dload folder of external storage.
third, turn off the phone , and press vol up + vol down + power button together to enter forced update mode.
if it is successful system will boot and you should flash android M firmware using dload method then u should unlock bootloader,install twrp,wipe /system /cache /data and then flash update.zip(android N) and hw_data of your firmware one after another.
i hope this help you.
still phone is not booting
I redownload b322, extracted Boot.img System.img Recovery.img Recovery2.img and Cust.img with
http://forum.xda-developers.com/showthread.php?t=2433454 Update Extractor
Flashed all .img true fastboot
But still nothing
Stuck on bootloader screen "Your device is unlocked, and can't be trusted"
Maybe i need flash some more images from b322.
Its look like phone cant pass bootloader.
Any sugestions?
P.S. Phone still have warranty, but booloader is unlocked
and fastboot oem relock ************** ends with failed.
"Failed - root cant trusted"
Sugestions how to lock it?
I had my phone bricked from testing cm, and going back to stock. My solution was to flash dload and recovery from the 182, followed by dload flash of 182.
@richish
caution : these commands will format the partition
can u use these command ?
"fastboot format /system"
"fastboot format /data"
or "fastboot erase /system"=> this will erase system partition
Phone is live now.
I downloaded DC-Phoenix and bought 15 credits
flashed stock B182 via DC-phoenix and phone booted.
I recomand this apllication for everybody who have similar problems.
THX for everybody who helpped.
richish said:
Phone is live now.
I downloaded DC-Phoenix and bought 15 credits
flashed stock B182 via DC-phoenix and phone booted.
I recomand this apllication for everybody who have similar problems.
THX for everybody who helpped.
Click to expand...
Click to collapse
How can i sign up for an account, it alway said wrong username or password !:crying:
DC-Phoenix is not cheap but it also cured my phone after bricking it with flashfire where all other methods did not work.
if you use it follow the instructions carefully and do the 2 step flashing although it will work after the first one. if you don`t do the second flash the partition sizes are wrong and a dload update will fail.
smartmobee said:
How can i sign up for an account, it alway said wrong username or password !:crying:
Click to expand...
Click to collapse
First u must buy credits, activate your account in email and then login in aplication.
Hi everyone
I would like to share the problem that i am having with my p9 , so maybe i can get your help.
Firstly i had L19C185 version and i changed Oeminfo in order to install c636 Beta 7.0 Nougat.
I installed the nougat but then realized that i dont have stock apps in my phone, so by mistakely tried to install TWRP for 6.0 Marshmallow and my problem started here.
Now my phone can not boot. its stuck in Phone is booting now ( the screen when you unlock bootloader after huawei logo) , and its never booting. it stays like that.
I tried to flash rboot.img , recovery.img and System.Img from fast boot. but whenever im trying to flash system.img after boot and recovery.img, a get an error and never succeeded to flash system.img. Im trying to flash these .img files from L19C636b180.
Can you please help me or give me some advice because none of mobile services couldnt fix and flash new software. maybe because they dont know exactly what should they do. and in my country i couldnt find anyofficial huawei service provider.
Please help me how to fix my phone.
I also had serious problems with flashing the thing back to stock.
TWRP was broken too for me.
I've done that to fix it all
The ONLY way that worked for me was
1. Download EVA-L19C636B168 from here http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586
2. Download that SRK tool http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
3. Flash the recovery from the SRK tool, you can do that with the tool or directly via fastboot (i don't know other proper source for the correct recovery img)
4. Put the image EVA-L19C636B168 (UPDATE.app) in the "dload" folder of your sd card
5. Start phone in dload mode (Hold all 3 buttons at start) and let the update do it's job
What about recovery??? Does 3 button combination works? Whats heppens if u hold volup and power button when turning phone on!
Situation looks similar what i had.
Only solution for me was dc-phoenix.
U have tu buy 15 points to flash phone (15eur) But it works.
I'm 99% sure that there are bootloader comands what is same as for dc-phoenix,but i dont know them.
Sent from my EVA-L19 using XDA-Developers mobile app
please help
i had bricked my p9 L09 twrp not working noting working only fastboot mode is working plzzz help me in finding boot.img recovery.img system.img

OP5 - Re-Lock Bootloader - Boot Screen Message: Your device has loaded a different OS

I've re-locked the boot-loader and done a full stock flash from Oneplus stock images, but now i get this warning when it boots up:
"Your device has loaded a different operating system. "
To remove this message pls follow the below steps
Install twrp
In TWRP Wipe everything including data. This will wipe internal storage
Connect to Pc when in Twrp
Copy Original OP5 ROM to phone
Install ROM
Do not reboot phone
Flash OP5 Original recovery from Twrp
Reboot to recovery
Then in OP5 recovery select reboot to fastboot mode
Then lock bootloader using 'Fastboot oem lock' command
Phone will reboot again with locked bootloader an no warning messages
Voila it's done
rahulns.xe said:
I've re-locked the boot-loader and done a full stock flash from Oneplus stock images, but now i get this warning when it boots up:
"Your device has loaded a different operating system. "
To remove this message pls follow the below steps
Install twrp
In TWRP Wipe everything including data. This will wipe internal storage
Connect to Pc when in Twrp
Copy Original OP5 ROM to phone
Install ROM
Do not reboot phone
Flash OP5 Original recovery from Twrp
Reboot to recovery
Then in OP5 recovery select reboot to fastboot mode
Then lock bootloader using 'Fastboot oem lock' command
Phone will reboot again with locked bootloader an no warning messages
Voila it's done
Click to expand...
Click to collapse
My case is when I try to reboot it to recovery it says "Your device has loaded a different operating system. " and showing oneplus boot animation, I have waited for almost 15-20 mins and it is not booting up. so now I cant get into bootloader, twrp, and system. What should I do now. Help me please
vipinw8 said:
My case is when I try to reboot it to recovery it says "Your device has loaded a different operating system. " and showing oneplus boot animation, I have waited for almost 15-20 mins and it is not booting up. so now I cant get into bootloader, twrp, and system. What should I do now. Help me please
Click to expand...
Click to collapse
Can you get into fastboot and try and flash TWRP from there? Or even try and flash the full system image over ADB?
dunjamon said:
Can you get into fastboot and try and flash TWRP from there? Or even try and flash the full system image over ADB?
Click to expand...
Click to collapse
HI, Thanks for the reply. I got access to TWRP and performed a format data (everything) and now its boot animation only, its been 15 mins and it is not booting up. what to do?
---------- Post added at 10:59 AM ---------- Previous post was at 10:51 AM ----------
vipinw8 said:
HI, Thanks for the reply. I got access to TWRP and performed a format data (everything) and now its boot animation only, its been 15 mins and it is not booting up. what to do?
Click to expand...
Click to collapse
HI. Its booted now. Damn it. thanks buddy. btw how to lock it again?
vipinw8 said:
HI, Thanks for the reply. I got access to TWRP and performed a format data (everything) and now its boot animation only, its been 15 mins and it is not booting up. what to do?
---------- Post added at 10:59 AM ---------- Previous post was at 10:51 AM ----------
HI. Its booted now. Damn it. thanks buddy. btw how to lock it again?
Click to expand...
Click to collapse
One of these commands usually does the trick.
fastboot oem lock
fastboot flashing lock
fastboot oem relock
the easiest way is unbrick tool,remembering backup everything you need.
or just flash oxygen in twrp,after boot up and back to fastboot with locking bl

Categories

Resources