However, if you are watching this, it means ur phone is bricked with huawei p10 lite/p10/p10 plus
Read the replies and follow the instruction noted by @Blackball and his links.
Then you will find you self a way to restore the phone.
Thanks again to @Blackball and rest of you guys, much appreciated for your help.
What on earth is Yoroot?
So, You can't enter fastboot mode am i right ?
Do you connect usb cable to your devices before press Vol- and Power button ?
Current Situation
After the battery was dead, i actually can enter the fastboot and i used TWRP 3.1.1 for huawei P10 Plus from github. double wiped my device and by far i have entered the system normally.
However, the ROM wasn't official and i lost my warranty for unlock my huawei phone. And the custom service from Huawei said that they don't provide any official ROM Since it's Android 7.0 .
This ROM is really crappy that i can't delete/uninstall any Application i installed.(It gets reboot everytime i try to and the Application is still there even i just tried to Delete/Uninstall).
Worst of all, some options does not work properly in "Option" menu . (For example i can't access to "Developer mode" that everytime i press it it tabbed back to the former menu.)
I really hate this crappy menu so i tried to search on the internet for P10 Plus ROM so far i get B133 update ROM i can find and i tried to install it from SDcard by pressing VOL - and VOL + and Power buttom.
It says failed to update system at 5% while updating/recoverying the system.
and the ROM which i'm using was found in HUAWEI's official fan forum from Club.Huawei.com a forum belongs in china.(Rooted rom B140).
Right now seems the only option for me is to find a better ROM than this .(At least won't get me so many bugs like this one .:crying: )
and Thanks for your comment "Bigbearxl" it worked as normally it should after the battery was dead then i recharged it.
Yet Right now the PC doesn't recognize the device though Via-Usb because it's not Huawei official ROM and Hisuite helper only recognize their own ROM and the rest Phone helper or ADB can't recognize the device while The Phone is Booting normal .
And Reply to "Craphead" Yoroot is a special Root tool for Huawei P10/P10 plus made by chinese from Huawei Fan Club forum.
New Update
After rewrited boot.img though fastboot mode from https://forum.xda-developers.com/p10/help/root-huawei-p10-p10-t3589946 thanks to "yury_z, " i can start to delete files with current system, but it's still crappy that it doesn't even have camera
So i think i will try dload method to recovery my phone with firware that i found in forum.
Failed
Looks like i have to stock with that bit longer
dload with update.app method failed. and recovery TWRP install missing md5.
Unless i get System.img or i guess i can't get another system.:crying:
This work for P10plus too
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
WackyJoker said:
Looks like i have to stock with that bit longer
dload with update.app method failed. and recovery TWRP install missing md5.
Unless i get System.img or i guess i can't get another system.:crying:
Click to expand...
Click to collapse
Maybe you could also try installing stock firmware with funkyhuawei, it's not for free though. But dload method never works on P10/plus unfortunately.
thanks @Blackball and @Craphead. i checked both of your method but didn't work and this new twrp 3.1.0 i downloaded displayed sd card 0mb. and i followed poster's step and missing one file.
However i might found a useful Thead that might work and i'm gonna try tonight.
http://www.stechguide.com/huawei-p10-plus-b133-nougat-update/
That is what I wrote.
It seems that firmware finder work for P10/plus now.
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder
@Blackball not sure you what you mean by that, do you mean that you can actually use it to install firmware on p10/p10 plus now? If so how did they manage to get around the authentication issue?
I debranded my phone from L09 to L29 DualSim with this guide. It work with moded stock recoverys.
Blackball said:
That is what I wrote.
It seems that firmware finder work for P10/plus now.
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder
Click to expand...
Click to collapse
well i tried your method but there were some file that can't be downloaded from that post so i used another and,eventhough with complete files, the method i posted and i was going to use it tonight. Failed.
did all the steps from update.bat indicated and all worked fine till the last step that it says " automaticly install system" and the phone shows error at recovery.(similar to dload method because it automaticly create dload and exact those ROM files)
it indicates a big red " ! " sign and stopped. basicly i'm back to "No System Status"
The only method wowrks for my "P10 Plus" is " flash system system.img " method.
yet i don't know how to exact system.img boot.img recovery.img etc from those stock firmware like those chinese.
i have some of their rewrote roms (it's crappy because i has no default camera and it's for chinese P10 Plus A.K.A VKY_L29) .
Yet i can't find any System.img on google by far.
Blackball said:
I debranded my phone from L09 to L29 DualSim with this guide. It work with moded stock recoverys.
Click to expand...
Click to collapse
I haven't tried your Firmware Finder method , i think i can install crappy system.img then try your Firmware Finder method.
Because right now i wiped my system and i'm without system :crying:
Guys This Thead https://forum.xda-developers.com/showthread.php?t=2315547
tells you how extract flashable rom files from firmware update.app.
It should work but i only made to Unknownfile XX .img and i can't download his script "HuaweiFinder" from his google drive.
Holy Crap it worked, i Extracted system.img and other img from update.app by some Chinese scripted unpack script. and I'm trying to restore my device though fastboot mode with adb.
Blackball said:
That is what I wrote.
It seems that firmware finder work for P10/plus now.
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder
Click to expand...
Click to collapse
well just tried your method and at last step it says installing failed. then i reboot entered rec mode choose wipe/factory reset
wiped till 50% and stopped, it can't factory reset.
Before this method fastboot mode was " Phone unlock " " Bootloader unlock."
Now it's just "Phone unlock"
now i'm stuck at boot loop "your device is booting now" then it rebooted and back to "your device is booting now" again then automaticly goes to Erecovery mode. I have to shutdown device for now and hope i can find some solution tomorrow :S
When you try this :
https://forum.xda-developers.com/showthread.php?t=3593108
It's important that you have the 3 zip files from your wanted firmware and rename them correctly. Don't mix with another firmwares.
Blackball said:
When you try this :
https://forum.xda-developers.com/showthread.php?t=3593108
It's important that you have the 3 zip files from your wanted firmware and rename them correctly. Don't mix with another firmwares.
Click to expand...
Click to collapse
i did this method yesterday and, well, i can't get update_full_VKY-L09_hw_eu.zip from the link : http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1475/g104/v85029/f1/full/filelist.xml . only Update.zip and Update_full_data.zip . the other one "update_full_VKY-L09_hw_eu.zip" i had to get it from another webside (it's also b133)
it shows a big "!" sign at the last step . i did everything it tells and tried both sdcard&script way to flash twice both rebrand&same brand update.
after the failure i can't enter "Vol +" and "Vol -" and "Power button" to do dload method . When i try to do that it just goes in Recovery mode.
In recovery mode i tried to wipe data/factory reset. It stopps at 50% which is after wipe and starting to factory reset at 50% it failed.
i try to flash in system.img and boot.img yet i still can not enter the system and stuck at bootloop.
Related
Hello,
I own a Huawei P8 L09, bootloader unlocked, rooted and with TWRP recovery.
I tried this morning to flash a new rom using TWRP recovery.
Problem is that I do believe I wiped to many partitions and I ended up with a bootloop.
I could at first access 3 times the emui erecovery (btw, Wifi recovery failed) but not anymore (is it related to the battery level ? I don't know how much I still have)
Following a lot of threads here and on some other forums (I've been searching now for approx. 7 hours...) :
I downloaded a update stock ROM (B170 something), I extracted Boot, System, Recovery and Cust
I entered bootloader mode (it's the only mode I can go to; recovery No, Download mode neither)
and on my computer I typed in the cmd "fastboot flash recovery recovery.img" same with system, cust and boot.
All of them said "Okay" but the bootloop is still there and I can't acess any other mode or shut the device off.
Also, my bootloader indicate that i'm "unlocked" but when I try to do something as :
"fastboot erase cache" it says "remote: not allowed" or something like that.
I tried the SD card flash method but I can't even acess the 3-button mode (doesn't work - bootloop again).
Finally, I've got 2 questions :
1) Is there a solution ? Is there/was there anybody in the same situation ?
2) Does the battery level influence wether I may or not enter any mode ? like b.e. under 30% I can't access recovery or something like that ?
Thanks in advance for your help and sorry for my bad english.
Greetings from Belgium !
Jules
Hi!
I have the same situation as you do, All i know is that you can access the eRecovery only if you're plugged in.
But it's completely useless. Have you found any solutions yet?
Edit:
i struggled and i'm still struggling but i figured out that I need the recovery and boot img of the version i was on previously. In my case that is B350.
The main mirror is down but i managed to find another one: https://mega.nz/#!NAcgQY7Y!I4eRfkaq62J31csv_wZ8_nTzmUbWPX71JUicDysjus8
after flashing them i was able to partially flash (using vol+-&pwr) B170 (it only went up to 90% with my USB attached, fails without USB)
At my surprise it booted B170 even if it didn't complete, however right now it keeps rebooting every minute. I'll update if i manage to fix this
I have the same problem as you both. To flash boot.img and other files by fastboot we need to unlock bootloader. To unlock bootloader we need to have Imei, Product Id and SN, but I can't read it because phone won't turn on.
Anyone know how to get this info?
you can read these info from the packaging box!
I managed to fix my issues (i believe) by continuously flashing and flashing versions. I never really managed to fully OTA update to 100% due to some "CUST error" but from B350 i managed to "update" to B170, then to B200, then to B321a.
Now i just installed TWRP and rooted it and on the process of installing xposed (if possible).
I wasted a good 6-7 hours on everything already
Well now I actually sent my phone in repair, given that it still was under warranty.
If they return it unrepeared, i will try it your way, Nikooo777. Thanks.
TukAliveFra said:
Well now I actually sent my phone in repair, given that it still was under warranty.
If they return it unrepeared, i will try it your way, Nikooo777. Thanks.
Click to expand...
Click to collapse
you gonna pay for the repair..
Hello everyone, I have a huawei p8 vodafone it branded.
I decided to root it, unblocked the bootloader and everything was good so far...
I tried to flash a custom recovery but failed for some reason and I decided to stick with stock recovery.
Now I installed an app as system app and my phone got bricked. my fault..
At first It went trough a bootloop and I was not able to access the huawei recovery or the fastboot, after a while it started to boot into a error message where it was saying that it was impossible to read user data partition, and give me some choices like backup, update to the latest version, or data factory.. I choose data factory twice but it went trough a bootloop again only to give me back to the same page after a while.
I can access huawei erecovery but it gives me getting info package failed when it says that I have to update it with wifi.
I can access fastboot mode and it says me that the phone is unlocked.
I really don't know what to do as I'm not expert, I tried to read various topics but never saw anyone with this message where it was saying impossible to read user data partition..
I had emui 3.1 5.1.1 with vodafone it brand... In case I have to flash it which firmware I should look for? Or is there a way to get my phone alive again without flashing?
http://forum.xda-developers.com/huawei-p8/how-to/guide-how-to-unbrick-huawei-p8-failed-t3260704
silvano2 said:
http://forum.xda-developers.com/huawei-p8/how-to/guide-how-to-unbrick-huawei-p8-failed-t3260704
Click to expand...
Click to collapse
Hey thank you silvano, can you tell me which firmware I need to flash it? Is it okay if I use a b170 even if I had the 5.1.1 emui 3.1 version?
Nothing, I can't seem to make it work, I've flashed the boot.img recovery.img system.img and cust.img successfully(b170) but still stuck in bootloop, I can enter bootloader mode, and recovery.. but when I enter recovery it says me that I need to update it and I can't update it because it says me that getting info package failed... tried with different wifis, same result..... The excatly same thing happens with the b132 stock rom too and I cant factory reset or even wipe cache if I dont make this update first as is the only option avaible on huawei eRecovery.
As last attemp I tried to force an upgrade with putting UPDATE.APP inside the sdcard and press vol up vol down and power for booting but this combination of buttons doesnt work...
I'm hopeless, I really don't know what to do... any help would be much appreciated
Hi everybody, i soft bricked my lovely Nova, here is the situatiuon :
- I tried to update the phone with the Emui 5 OTA zip but the phone turned off and now won't boot anymore
- When i try to boot normaly, it show the Huawei eRecovery and fail to recover the phone
- I can boot on fastboot mode / rescue mode
- I have TWRP installed and can boot on it but when i try to flash the can-L11c432.zip supplied by MORPH, it says "Failed to mount '/cust'" and stops here.
I really don't know what to do, moreover i lost the backup i made with TWRP.
If someone can help me i'll offer him a meal (paypal)
Sorry for my bad english and have a nice day everyone.
Hi Keezle,
here is the recovery.img from the EMUI5 Beta Update. Flash it with fastboot and apply the update once again (Boot with Power + Vol down + Vol up) After the Update is complete make a full wipe in the stock recovery.
You need a external SD Card with the dload folder thats include the Update.
Keezle said:
Hi everybody, i soft bricked my lovely Nova, here is the situatiuon :
- I tried to update the phone with the Emui 5 OTA zip but the phone turned off and now won't boot anymore
- When i try to boot normaly, it show the Huawei eRecovery and fail to recover the phone
- I can boot on fastboot mode / rescue mode
- I have TWRP installed and can boot on it but when i try to flash the can-L11c432.zip supplied by MORPH, it says "Failed to mount '/cust'" and stops here.
I really don't know what to do, moreover i lost the backup i made with TWRP.
If someone can help me i'll offer him a meal (paypal)
Sorry for my bad english and have a nice day everyone.
Click to expand...
Click to collapse
I came to a similar situation. The CUST supplied by Morph seems not to be flashable. Untick the CUST when flashing the NANDROID. It will go through the process and the phone will eventually boot again.
-=MoRpH=- said:
Hi Keezle,
here is the recovery.img from the EMUI5 Beta Update[/URL]. Flash it with fastboot and apply the update once again (Boot with Power + Vol down + Vol up) After the Update is complete make a full wipe in the stock recovery.
You need a external SD Card with the dload folder thats include the Update.
Click to expand...
Click to collapse
Si, i put the C432B320 update.zip in dload folder on an external SD Card, i flashed the Emui 5 beta update recovery successfully, but when i boot with Power + Vol down + Vol up it starts the installation and stops at 5% saying "Software install failed !". Should i use another update.zip file ?
Thank you MORPH
Keezle said:
Si, i put the C432B320 update.zip in dload folder on an external SD Card, i flashed the Emui 5 beta update recovery successfully, but when i boot with Power + Vol down + Vol up it starts the installation and stops at 5% saying "Software install failed !". Should i use another update.zip file ?
Thank you MORPH
Click to expand...
Click to collapse
Maybe unpack the C432B320 until you have an update.app in dload folder. I did that and flashed the ROM. The first try was a failure and I had to restore a NANDROID (bootloop). Currently, I'm trying to flash it again but now with the EMUI5 recovery morph has supplied.
System of a pWne!^ said:
Maybe unpack the C432B320 until you have an update.app in dload folder. I did that and flashed the ROM. The first try was a failure and I had to restore a NANDROID (bootloop). Currently, I'm trying to flash it again but now with the EMUI5 recovery morph has supplied.
Click to expand...
Click to collapse
I'll try this now thank you
Keezle said:
I'll try this now thank you
Click to expand...
Click to collapse
But be careful and have a backup. I just flashed it and it seems not to work again :/ It just keeps on sitting on the Huawei logo for minutes now. That's it.
System of a pWne!^ said:
But be careful and have a backup. I just flashed it and it seems not to work again :/ It just keeps on sitting on the Huawei logo for minutes now. That's it.
Click to expand...
Click to collapse
So now, it start installing update and says "installation failed !" at 50%
Keezle said:
So now, it start installing update and says "installation failed !" at 50%
Click to expand...
Click to collapse
What OTA do you currently try to flash? I currently try to give my luck to CAN-L11C432B320 even though I have a L01 device. http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v71311/f1/full/update.zip
If needed, i updated the link for the cust img...
http://forum.xda-developers.com/showthread.php?p=70294269
Same isseu with other update files, i think i have to wait for the full EMUI 5 firmware..
Keezle said:
Same isseu with other update files, i think i have to wait for the full EMUI 5 firmware..
Click to expand...
Click to collapse
hello I have the problem Software install failed! can you help me thanks in advance
better work with ADB and flash 3 main imgs....recovery,boot,system images...then reboot...then do the 3 buttons update
need help
Hello dear friends
Do not be tired
I need a dump file Huawei Can l11
The ears are burned and their hard drive is changed
If there is someone else's phone root, please give me a dummy file
thanks to everyone
today i want to share my sad story with u guys , i got my phone huawe mla-al10 , i flash custom rom lineage os 13.1 from xda for huawei can-11 then it got bootloop , before this i succesfully install it without bootloop , so i decide to reset , then i go to the recovery , idk how my recovery become the stock one ,then i click format data , suddenly its stuck at 61% then keep reboot , i open fastboot then get frp locked , im start panic , then i do a research how to get rid frp locked , they said relock the bootloader , then i relock booatlader , haa its getting more worse , now icant even go to fastboot or update mood , its only goes to factory reset lowlevel.... then screen becomes black with blue led , i connect to pc , i found hs-usb diagnostic 9006 ( com 3 ) thats mean i can unbrick only with 1 way , with Snapdragoon flashtool , but i cant find nowhere for the firmware that make to unbrick using flashtool for my devices , hmmm im so sad right now , is there any way i can make my own flashtool file for snapdragon flashtool ? i hope i can fix this as soon as possible
If ADB is working,just flash your original (firmware) RECOVERY,BOOT and SYSTEM.img from the update.app zip file...after flashing those 3 img file,just reboot via adb...fastboot reboot
Phone should be like new
virusdunil said:
If ADB is working,just flash your original (firmware) RECOVERY,BOOT and SYSTEM.img from the update.app zip file...after flashing those 3 img file,just reboot via adb...fastboot reboot
Phone should be like new
Click to expand...
Click to collapse
to make adb working i need to enable usb debugging bla4 but my phone is totally dead , no fastboot nothing i can do except go to edl modee
shazlieyazizan1 said:
to make adb working i need to enable usb debugging bla4 but my phone is totally dead , no fastboot nothing i can do except go to edl modee
Click to expand...
Click to collapse
same problem adb is also not working did you find any solution?
I am having a problem i didnt do anything with my phone its huawei nova plus just 1 or 2 day ago open the boxed and try to update it using firmware finder app after downloading the full ota phone automatically restart and stuck on installing update 5% and its still on boot loop am not able to flash any firmware using sd card or update.app just because it always failed on 5 % even though am not able to wipe factory/reset it also failing. Can you guys please help me? to solve the problem?
abuapka said:
same problem adb is also not working did you find any solution?
I am having a problem i didnt do anything with my phone its huawei nova plus just 1 or 2 day ago open the boxed and try to update it using firmware finder app after downloading the full ota phone automatically restart and stuck on installing update 5% and its still on boot loop am not able to flash any firmware using sd card or update.app just because it always failed on 5 % even though am not able to wipe factory/reset it also failing. Can you guys please help me? to solve the problem?
Click to expand...
Click to collapse
try get correct model from huawei updater finder ..
if dload method not work then try to go to fastboot mode by tgis way >> Turn off your mobile and just click and hold on DOWN vol then connect it with usb it should work !
Recently, I turned off developer options in my rooted S7 Edge (SM-G935FD). Idk if that is the cause, but after rebooting I got the error "Custom Binary Blocked by FRP Lock". I couldnt boot into my recovery (TWRP) either. I was running on Oreo btw. I watched some Youtube guides and apparently the solution was to flash stock rom. So... I flashed an Oreo Stock Rom on my phone via Odin. I thought that would solve my problem, but instead it made it worse. It didnt give me the Custom Binary Blocked by FRP lock error but my boot screen is stuck at the boot animation (not a bootloop). I could boot into the stock recovery tho. I tried a factory reset, that didnt make things better. I could also boot into download mode. I thought I made a mistake, so I flashed like 5-8 times with both CSC an Home_CSC. The result was the same, it would get stuck at the boot animation. I tried flashing TWRP via Odin too, but it said "Custom Binary (Recovery) blocked by FRP Lock". I tried sideloading that TWRP file to my device via ADB. It gave me an error too (I think "Cannot flash from external devices" or something like that) I thought flashing with Re-partition and Nand Erase On would solve my problem, so I tried that, but it didnt work. Im running on Binary 3 apparently. Is there anything I can do?
Rapidfayaround said:
Recently, I turned off developer options in my rooted S7 Edge (SM-G935FD). Idk if that is the cause, but after rebooting I got the error "Custom Binary Blocked by FRP Lock". I couldnt boot into my recovery (TWRP) either. I was running on Oreo btw. I watched some Youtube guides and apparently the solution was to flash stock rom. So... I flashed an Oreo Stock Rom on my phone via Odin. I thought that would solve my problem, but instead it made it worse. It didnt give me the Custom Binary Blocked by FRP lock error but my boot screen is stuck at the boot animation (not a bootloop). I could boot into the stock recovery tho. I tried a factory reset, that didnt make things better. I could also boot into download mode. I thought I made a mistake, so I flashed like 5-8 times with both CSC an Home_CSC. The result was the same, it would get stuck at the boot animation. I tried flashing TWRP via Odin too, but it said "Custom Binary (Recovery) blocked by FRP Lock". I tried sideloading that TWRP file to my device via ADB. It gave me an error too (I think "Cannot flash from external devices" or something like that) I thought flashing with Re-partition and Nand Erase On would solve my problem, so I tried that, but it didnt work. Im running on Binary 3 apparently. Is there anything I can do?
Click to expand...
Click to collapse
I still have the "FRP Lock: On" on download mode, so I tried bypassing FRP lock via binary 5 combination firmware and flashing a binary 7 stock firmware. This time, it doesnt get stuck at the boot animation, instead it redirects to a screen with an android face saying "Installing System updates". A few seconds later, it says "No command" with a dead android face. Then it reboots and the same thing happens. Basically a boot loop, but in a different way. I cant seem to boot to stock recovery either. The worst thing is that I cant even turn off the thing. I have to leave it loop for the entire day until its battery dies
Rapidfayaround said:
I still have the "FRP Lock: On" on download mode, so I tried bypassing FRP lock via binary 5 combination firmware and flashing a binary 7 stock firmware. This time, it doesnt get stuck at the boot animation, instead it redirects to a screen with an android face saying "Installing System updates". A few seconds later, it says "No command" with a dead android face. Then it reboots and the same thing happens. Basically a boot loop, but in a different way. I cant seem to boot to stock recovery either. The worst thing is that I cant even turn off the thing. I have to leave it loop for the entire day until its battery dies
Click to expand...
Click to collapse
after flashing the combination firmware, flash the stock firmware and go thru the boot process
Youdoofus said:
after flashing the combination firmware, flash the stock firmware and go thru the boot process
Click to expand...
Click to collapse
That is what I literally did. I flashed a combination firmware, factory rested my entire phone, turned on developer options as well as allow usb debugging, attempted to reset FRP via Z3X Samsung Tool Pro and finally flashed a stock rom. And, the result is this. A bootloop with an android face dying. I did manage to enter a different screen by pressing volume up once along with pressing volume down and power button. It said "could not open recovery_because_no file directory" and had some more errors. The thing is....I made it worse at the first place. I could have flashed a room with binary 6 or lower, cuz at least the combination firmware would have been available to flash, but my stupid brain did not think of that. I flashed a binary 7 stock rom and there is no combination firmware with a binary of 7 or more. Which means, I will most likely get the "SW check fail Device: 7 Binary: 6 " error while flashing.
Rapidfayaround said:
That is what I literally did. I flashed a combination firmware, factory rested my entire phone, turned on developer options as well as allow usb debugging, attempted to reset FRP via Z3X Samsung Tool Pro and finally flashed a stock rom. And, the result is this. A bootloop with an android face dying. I did manage to enter a different screen by pressing volume up once along with pressing volume down and power button. It said "could not open recovery_because_no file directory" and had some more errors. The thing is....I made it worse at the first place. I could have flashed a room with binary 6 or lower, cuz at least the combination firmware would have been available to flash, but my stupid brain did not think of that. I flashed a binary 7 stock rom and there is no combination firmware with a binary of 7 or more. Which means, I will most likely get the "SW check fail Device: 7 Binary: 6 " error while flashing.
Click to expand...
Click to collapse
If the device is still entering download mode, install the recent version of stock for your device. Maybe that will solve your problem.
Rapidfayaround said:
That is what I literally did. I flashed a combination firmware, factory rested my entire phone, turned on developer options as well as allow usb debugging, attempted to reset FRP via Z3X Samsung Tool Pro and finally flashed a stock rom. And, the result is this. A bootloop with an android face dying. I did manage to enter a different screen by pressing volume up once along with pressing volume down and power button. It said "could not open recovery_because_no file directory" and had some more errors. The thing is....I made it worse at the first place. I could have flashed a room with binary 6 or lower, cuz at least the combination firmware would have been available to flash, but my stupid brain did not think of that. I flashed a binary 7 stock rom and there is no combination firmware with a binary of 7 or more. Which means, I will most likely get the "SW check fail Device: 7 Binary: 6 " error while flashing.
Click to expand...
Click to collapse
the "no such file or directory" error is due to either having had removed stock recovery in flashing the firmwares or the factory recovery corrupted due to likely the same reason. Just flash a revision 7 firmware for your phone and it will at least boot
Dark Stranger said:
If the device is still entering download mode, install the recent version of stock for your device. Maybe that will solve your problem.
Click to expand...
Click to collapse
^^^ this ^^^
Dark Stranger said:
If the device is still entering download mode, install the recent version of stock for your device. Maybe that will solve your problem.
Click to expand...
Click to collapse
I have literally flashed the latest stock rom for my device and my country which is G935FXXS7ESK8.
I am a bit confused tho...I am not sure if my device is SM-G935FD or SM-G935F. The download mode says SM-G935F...but this phone used to work with a SM-G935FD rom back in the days. Is this causing the problem most likely? And btw the repair shop said they cant fix it too
Rapidfayaround said:
I have literally flashed the latest stock rom for my device and my country which is G935FXXS7ESK8.
I am a bit confused tho...I am not sure if my device is SM-G935FD or SM-G935F. The download mode says SM-G935F...but this phone used to work with a SM-G935FD rom back in the days. Is this causing the problem most likely? And btw the repair shop said they cant fix it too
Click to expand...
Click to collapse
I am somehow relieved to know that someone else on this planet is on the same (EXACT) boat as me....this is what we get for messing around too much with our phone hum?
1 - After booting up my phone I get the blue background with a dead Android and "No Command" message
2 - I tried accessing recovery by pressing Power+Home+VolumeUp, but all I get is a black screen with a wall of code lines with "fail to open recovery_cause(No such file or directory)" at the beggining of the text.
3 - "No problem! I'll just flash TWRP with ODIN and install a custom ROM and be done with it!".
..NOPE! FRP(factory reset protection) is ON!!! I cannot install TWRP
4- I've tried to find a combination file with binary version 7...but looks like the internet doesn't seem to care about the good ol' number 7...All I can find is binary version 6.
What Im trying to do now is creating my own combination file binary version 7 (if that's even a thing...) from a stock firmware. But I'm not getting any luckier down this path.
Looks like we need a hero...:crying:
PseudoNoob said:
I am somehow relieved to know that someone else on this planet is on the same (EXACT) boat as me....this is what we get for messing around too much with our phone hum?
1 - After booting up my phone I get the blue background with a dead Android and "No Command" message
2 - I tried accessing recovery by pressing Power+Home+VolumeUp, but all I get is a black screen with a wall of code lines with "fail to open recovery_cause(No such file or directory)" at the beggining of the text.
3 - "No problem! I'll just flash TWRP with ODIN and install a custom ROM and be done with it!".
..NOPE! FRP(factory reset protection) is ON!!! I cannot install TWRP
4- I've tried to find a combination file with binary version 7...but looks like the internet doesn't seem to care about the good ol' number 7...All I can find is binary version 6.
What Im trying to do now is creating my own combination file binary version 7 (if that's even a thing...) from a stock firmware. But I'm not getting any luckier down this path.
Looks like we need a hero...:crying:
Click to expand...
Click to collapse
OMGGGGGGGG....Looks like I am not the only one. DAMN. Bro...tell me if you find a solution ok? Hopefully there is a way to solve this problem...there has to be one. And share your combination firmware after you finish it. Thank you very much
Rapidfayaround said:
OMGGGGGGGG....Looks like I am not the only one. DAMN. Bro...tell me if you find a solution ok? Hopefully there is a way to solve this problem...there has to be one. And share your combination firmware after you finish it. Thank you very much
Click to expand...
Click to collapse
No luck over here friend...
Desperate times require desperate measures. Have you ever tried flashing combination files from different S7 Edge versions?
I can find files for the G935A with a revision 7 of the binary...Im thinking flashing it into my G935F and see what happens. I've read the risks associated with installing firmwares from other phone versions, but I'll have a paperweight either way.
I'll keep this thread updated.
Rapidfayaround said:
I have literally flashed the latest stock rom for my device and my country which is G935FXXS7ESK8.
I am a bit confused tho...I am not sure if my device is SM-G935FD or SM-G935F. The download mode says SM-G935F...but this phone used to work with a SM-G935FD rom back in the days. Is this causing the problem most likely? And btw the repair shop said they cant fix it too
Click to expand...
Click to collapse
Doesn't really matter if you have a F or FD. I'd say you flash the latest stock rom for G935F or FD(which ever is latest) for any country regardless. By this you should be able to boot and won't get any odin errors.
UsmaniMustafa said:
Doesn't really matter if you have a F or FD. I'd say you flash the latest stock rom for G935F or FD(which ever is latest) for any country regardless. By this you should be able to boot and won't get any odin errors.
Click to expand...
Click to collapse
Can you provide me the link plz.
Turns out, its a hardware problem with the storage. Replacing the motherboard might be the solution I think. :/
I had solved my phone last day
At first u can flash ur phone to leatest stock rom. Then u have to turn of frp lock. Then u will able to boot up your phone. If u cant fix u can knock me on facebook. (If u r a z3x user). Bcoz u need z3x for bypass frp with ufs cable.
Im also using s7 edge.
hazratboss said:
At first u can flash ur phone to leatest stock rom. Then u have to turn of frp lock. Then u will able to boot up your phone. If u cant fix u can knock me on facebook. (If u r a z3x user). Bcoz u need z3x for bypass frp with ufs cable.
Im also using s7 edge.
Click to expand...
Click to collapse
Oh ok I will contact you
hazratboss said:
At first u can flash ur phone to leatest stock rom. Then u have to turn of frp lock. Then u will able to boot up your phone. If u cant fix u can knock me on facebook. (If u r a z3x user). Bcoz u need z3x for bypass frp with ufs cable.
Im also using s7 edge.
Click to expand...
Click to collapse
Does it matter if I use the cracked version without box. And no, I dont have the ufs cable. Is there anything else I can do?
Hi guys, I have the exact same problem with my S7 edge from T-mobile (g935t). Odin will only accept for flash the latest rom and after flash it reboots but I get BSOD. I tried a pit file also from an old g935T rom which was android 6.0 and I managed to get into recovery for a moment and I did a factory reset/wipe cache but after reboot entered again in a black screen and the blue led was lit. I finally removed the battery to turn the phone off. I can still enter download mode but is there anything else I can do to resurrect the phone?
Samsung s7 edge (g935f)
Hi everyone , please am having issue of NO COMMAND and i cant boot into recovery. My oem is on so i cant install twpr neither. Am on binary u8. Please any solution to recover my phone?
Very very good new guys...yep you guessed it right. I was able to fix this problem.
How you may ask? Follow these steps
Note: Make sure you have enough battery. Lack of battery charge in my case caused alot of problems.
1. Download a U7 Rom for your SM-G935F or SM-G935FD
2. Extract the Rom as well as the AP
3. After you extract the AP, you will be greeted with boot.lz4.img , recovery.lz4.img , system.lz4.img & meta-data
4. Make a backup of recovery.lz4.img and meta-data just in case. Also, make a copy of boot.lz4.img and rename the copied one to recovery.lz4.img. Don't forget to delete the original recovery and meta-data
5. Now, you should be left with boot.lz4.img , (modified) recovery.lz4.img and system.lz4.img.
6. Now, download this https://www.mediafire.com/file/ah20ha869prdkkc/Autotar2.0_By_FixFirmwares.com.rar/file
7. Now, make a .md5 file that contains (modified) recovery.lz4.img and system.lz4.img
8. After you are done making that .md5, flash it along with CSC, CP and BL.
9. You should directly boot into your device, (if you do), charge your phone for a while if the battery is lower than 20%.
10. Then, go to the settings and enable OEM Unlock before doing ANYTHING
11. Then, reboot to download mode and flash TWRP
12. Download the no-verity-encryption.zip
https://zackptg5.com/android.php#disverfe
13. Allow system modifications and format data (NOT WIPE)
14. If that doesn't work, go to TWRP, connect it to your PC and copy the no-verity-encryption.zip file and install it
15. If that still doesn't work then, follow this tutorial
https://www.google.com/amp/s/forum....niversal-dm-verity-forceencrypt-t3817389/amp/
16. Then, you should boot and yea...enjoy ?
If this method doesn't work then, you need to try different combinations.
Try packing these files in AP
1. Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
2. (Modified) Recovery.lz4.img & system.lz4.img
3. Meta-data, Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
If that doesn't work, I'm sorry this is how I fixed it. ?*
For anyone wondering how I fixed it well, firstly a HUGE THANKS TO @shah22 & @Tapas27sTapas2. This would have been LITERALLY IMPOSSIBLE WITHOUT THEM. So, basically I tried an AP with renamed recovery.lz4.img and system.lz4.img only along with CP, CSC and BL. Due to my phone having literally 0%, this journey was very difficult.
Feel free to ask any question
Very very good new guys...yep you guessed it right. I was able to fix this problem.
How you may ask? Follow these steps
Note: Make sure you have enough battery. Lack of battery charge in my case caused alot of problems.
1. Download a U7 Rom for your SM-G935F or SM-G935FD
2. Extract the Rom as well as the AP
3. After you extract the AP, you will be greeted with boot.lz4.img , recovery.lz4.img , system.lz4.img & meta-data
4. Make a backup of recovery.lz4.img and meta-data just in case. Also, make a copy of boot.lz4.img and rename the copied one to recovery.lz4.img. Don't forget to delete the original recovery and meta-data
5. Now, you should be left with boot.lz4.img , (modified) recovery.lz4.img and system.lz4.img.
6. Now, download this https://www.mediafire.com/file/ah20ha869prdkkc/Autotar2.0_By_FixFirmwares.com.rar/file
7. Now, make a .md5 file that contains (modified) recovery.lz4.img and system.lz4.img
8. After you are done making that .md5, flash it along with CSC, CP and BL.
9. You should directly boot into your device, (if you do), charge your phone for a while if the battery is lower than 20%.
10. Then, go to the settings and enable OEM Unlock before doing ANYTHING
11. Then, reboot to download mode and flash TWRP
12. Download the no-verity-encryption.zip
https://zackptg5.com/android.php#disverfe
13. Allow system modifications and format data (NOT WIPE)
14. If that doesn't work, go to TWRP, connect it to your PC and copy the no-verity-encryption.zip file and install it
15. If that still doesn't work then, follow this tutorial
https://www.google.com/amp/s/forum....niversal-dm-verity-forceencrypt-t3817389/amp/
16. Then, you should boot and yea...enjoy ?
If this method doesn't work then, you need to try different combinations.
Try packing these files in AP
1. Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
2. (Modified) Recovery.lz4.img & system.lz4.img
3. Meta-data, Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
If that doesn't work, I'm sorry this is how I fixed it. ?*
For anyone wondering how I fixed it well, firstly a HUGE THANKS TO @shah22 & @Tapas27s. This would have been LITERALLY IMPOSSIBLE WITHOUT THEM. So, basically I tried an AP with renamed recovery.lz4.img and system.lz4.img only along with CP, CSC and BL. Due to my phone having literally 0%, this journey was very difficult.
Feel free to ask any question