Hello guys , i have a very very big problem here .
So lets start from the beggining :
- i was going to flash RR v5.8.2 through twrp 3.0.2-0 , i backed up boot and data from my stock , and then flashed .
- everything was ok , phone booted into RR , i was customising my android for 1 hour and then decided to restore that backup i made .
- i booted into recovery , restored the backup , and BOOOOM THE PHONE GOT BOOTLOOP
From here i tried dload method .
- put c900b300 or whatever .. UPDATE.APP file on my dload folder from sd card ( with my old phone )
- boot into 3 buttons method .
- flashed , and THEN AGAIN BOOTLOOP , BUT THIS TIME IN "your device has been unlocked and can't be trusted."
I have unlocked bootloader , frp unlocked ... no usb debugging enabled .
And can't get to erecovery , can't get to 3 buttons method . Its just stuck on "Your device is booting now..."
Please help me guys , i have this phone for 5 days only and I already broke it...
This what happens when you don't follow the instructions.
Buy a new motherboard.
Johnny TDN said:
This what happens when you don't follow the instructions.
Buy a new motherboard.
Click to expand...
Click to collapse
Sorry but that's bull****!
No need to buy a new mobo. Just use one of the many downgrade guides and be on your merry way.
A full,. hard brick is pretty hard to get. You'll be ok, OP.
Johnny TDN said:
This what happens when you don't follow the instructions.
Buy a new motherboard.
Click to expand...
Click to collapse
I solved it .
hexxr said:
I solved it .
Click to expand...
Click to collapse
Since you aren't writing HOW you solved it, i will leave here my solution for other ppl
had this problem yesterday & solved it by myself.
u will need fastboot for this
1. Boot phone into fastboot (shut down completely, plug phone in to your pc while you're holding down the "VOL -" Button
2. now download this TWRP Recovery (https://forum.xda-developers.com/huawei-p9lite/development/recovery-twrp-huawei-p9-lite-t3491847)
3. put the img file in the same folder as the "fastboot.exe"
4 go to the folder where your files are. hold shift and do a right click into your folder. Choose "Open Command Prompt here"
5. type in "fastboot devices" -- if your device is showing up then you can continue
6. type in "fastboot flash recovery FILENAME.img" (Change filename to the name of the recovery image)
7 If everything worked, shut down your phone.
8. Hold "Vol +" and the power button
The "untrusted device" screen will come. just pass it.
If everything worked and you're in the recovery then you can install every rom zip you want till ur phone works again
If something doesn't work or something is not clear then don't be afraid to ask
.... i hope i wrote everything right xD
zgomot said:
Sorry but that's bull****!
No need to buy a new mobo. Just use one of the many downgrade guides and be on your merry way.
A full,. hard brick is pretty hard to get. You'll be ok, OP.
Click to expand...
Click to collapse
if he couldn';t even boot in fastboot,,,then a new motherboard was required.
Johnny TDN said:
if he couldn';t even boot in fastboot,,,then a new motherboard was required.
Click to expand...
Click to collapse
You see, he eventually managed to boot into fastboot, so your rash comment about getting a new motherboard was, well... kind of rash.
zgomot said:
You see, he eventually managed to boot into fastboot, so your rash comment about getting a new motherboard was, well... kind of rash.
Click to expand...
Click to collapse
most of the times, Fastboot may save you or not (50/50) when you have a hard brick
hexxr said:
I solved it .
Click to expand...
Click to collapse
HOW? there's plenty of people which hasn't been able to solve it... please share...
islandman75 said:
HOW? there's plenty of people which hasn't been able to solve it... please share...
Click to expand...
Click to collapse
I can't remeber , now I have iPhone 5S , so yea..
kennyweed said:
Since you aren't writing HOW you solved it, i will leave here my solution for other ppl
had this problem yesterday & solved it by myself.
u will need fastboot for this
1. Boot phone into fastboot (shut down completely, plug phone in to your pc while you're holding down the "VOL -" Button
2. now download this TWRP Recovery (https://forum.xda-developers.com/huawei-p9lite/development/recovery-twrp-huawei-p9-lite-t3491847)
3. put the img file in the same folder as the "fastboot.exe"
4 go to the folder where your files are. hold shift and do a right click into your folder. Choose "Open Command Prompt here"
5. type in "fastboot devices" -- if your device is showing up then you can continue
6. type in "fastboot flash recovery FILENAME.img" (Change filename to the name of the recovery image)
7 If everything worked, shut down your phone.
8. Hold "Vol +" and the power button
The "untrusted device" screen will come. just pass it.
If everything worked and you're in the recovery then you can install every rom zip you want till ur phone works again
If something doesn't work or something is not clear then don't be afraid to ask
.... i hope i wrote everything right xD
Click to expand...
Click to collapse
I bricked my phone when trying to downgrade from 7.0. I have bootloader unlocked and can get into fastboot screen but when I flash the recovery i get "FAILED (remote: Command not allowed)".
They say that P9 Lite drivers should be installed (usually installs when Hisuite detects the phone). Unfortunately, I'm using a new PC. Or correct me if I'm wrong.
---------- Post added at 07:24 AM ---------- Previous post was at 06:47 AM ----------
Ok just figured it out thanks to this post: https://forum.xda-developers.com/huawei-p9lite/help/flash-recovery-failed-remote-command-t3555563
it looks like a bug that says bootloader is unlocked even if it isn't. So just perform another bootloader unlock and go back to fastboot screen. You should be able to flash images now.
I have the same problem:
"FAILED (remote: Command not allowed)"
Any solution for this problem? I Cant boot into OS (boot loop). Fastboot and recovery are possible.
bonnerable said:
I bricked my phone when trying to downgrade from 7.0. I have bootloader unlocked and can get into fastboot screen but when I flash the recovery i get "FAILED (remote: Command not allowed)".
They say that P9 Lite drivers should be installed (usually installs when Hisuite detects the phone). Unfortunately, I'm using a new PC. Or correct me if I'm wrong.
---------- Post added at 07:24 AM ---------- Previous post was at 06:47 AM ----------
Ok just figured it out thanks to this post: https://forum.xda-developers.com/huawei-p9lite/help/flash-recovery-failed-remote-command-t3555563
it looks like a bug that says bootloader is unlocked even if it isn't. So just perform another bootloader unlock and go back to fastboot screen. You should be able to flash images now.
Click to expand...
Click to collapse
Related
Hi i need to unroot and factory reset the phone. Oneplus 2 What ive already done or tried: I started to try unrooting it through superSU but that didnt work i just waited waited and nothing hapened. so then i tried to fastboot img but just got error the device is locked even though i did enable oem unluck and usb debuging. so then i wrote in cmd: fastboot oem unlock and now the phone starts up to the op logo then restard into it again after a second D'=
Im not familiar with forums and very stressed to get my phone working so i would be very very gratefull for help.
now i cant even charge it the batery logo doesnt come up after i did fasboot oem unlock again.... rip
spacebite said:
Hi i need to unroot and factory reset the phone. Oneplus 2 What ive already done or tried: I started to try unrooting it through superSU but that didnt work i just waited waited and nothing hapened. so then i tried to fastboot img but just got error the device is locked even though i did enable oem unluck and usb debuging. so then i wrote in cmd: fastboot oem unlock and now the phone starts up to the op logo then restard into it again after a second D'=
Im not familiar with forums and very stressed to get my phone working so i would be very very gratefull for help.
Click to expand...
Click to collapse
spacebite said:
no i cant even charge it the batery logo doesnt come up after i did fasboot oem unlock again.... rip
Click to expand...
Click to collapse
Got to OnePlus support center and go in download section and download official ROM. Hold power and volume up bottons and connect it to PC. After that go in folder where adb files are located on your PC (If you don't have them, search on Google for "adb install 15 sec"). Hold left shift on your keyboard and right click your mouse in that folder on an empty space. Click something related with command window and type "fastboot devices". If you get some kind of feedback it's 2minute of work! If you don't have anything come up, try to start your device in fastboot mode again (second sentence in this post). After you got a feedback from command "fastboot devices" flash custom recovery (I suggest TWRP, Google it and download the .IMG file for your device). To flash a custom recovery type this in command line: "fastboot flash recovery IMAGE_NAME.img"
*replace IMAGE_NAME with actual image name...
After that boot in recovery by disconnecting the phone and powering off the phone. Press and hold power button and volume down buttons till blue TWRP logo appears. After that connect your device on PC and transfer your .Zip file(ROM) to internal memory of your device. You should go back to main menu of recovery and select wipe>advanced wipe, select everything BUT INTERNAL STORAGE!!!***IMPORTANT***
Then you just install ROM like you would normally do...
Press thanks it i helped! Hope I didn't missed something.
This is written in mind with that you have unlocked bootloader like you have written in your post...
x8Cooler said:
Got to OnePlus support center and go in download section and download official ROM. Hold power and volume up bottons and connect it to PC. After that go in folder where adb files are located on your PC (If you don't have them, search on Google for "adb install 15 sec"). Hold left shift on your keyboard and right click your mouse in that folder on an empty space. Click something related with command window and type "fastboot devices". If you get some kind of feedback it's 2minute of work! If you don't have anything come up, try to start your device in fastboot mode again (second sentence in this post). After you got a feedback from command "fastboot devices" flash custom recovery (I suggest TWRP, Google it and download the .IMG file for your device). To flash a custom recovery type this in command line: "fastboot flash recovery IMAGE_NAME.img"
*replace IMAGE_NAME with actual image name...
After that boot in recovery by disconnecting the phone and powering off the phone. Press and hold power button and volume down buttons till blue TWRP logo appears. After that connect your device on PC and transfer your .Zip file(ROM) to internal memory of your device. You should go back to main menu of recovery and select wipe>advanced wipe, select everything BUT INTERNAL STORAGE!!!***IMPORTANT***
Then you just install ROM like you would normally do...
Press thanks it i helped! Hope I didn't missed something.
This is written in mind with that you have unlocked bootloader like you have written in your post...
Click to expand...
Click to collapse
thanks i will try when i get home
Fallow this and don't trust any guides written out of memory with likely any mistakes.. (no offense)
This guide has various approaches to recover your phone, remember to research first and don't type carelessly any adb commands, it's not enough to just tick "oem unlock" in developer options, you'd have to type command on fastboot too, to unlock the bootloader.. there are many guides and youtube tutorials on this subject, absolutely unnecessary to blindly kill it, anyways I'll never understand how you can be so reckless with your phone..
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Edit: the state you brought your phone into is called "hard bricked" - have fun..
Sent from my OnePlus2 using XDA Labs
spacebite said:
thanks i will try when i get home
Click to expand...
Click to collapse
Don't!
If you get no joy from following the instructions in the link given by @Sam Nakamura, try @fareed_xtreme's Official OP2 Stock Reset to OOS 3.0.2
Sam Nakamura said:
Fallow this and don't trust any guides written out of memory with likely any mistakes.. (no offense)
This guide has various approaches to recover your phone, remember to research first and don't type carelessly any adb commands, it's not enough to just tick "oem unlock" in developer options, you'd have to type command on fastboot too, to unlock the bootloader.. there are many guides and youtube tutorials on this subject, absolutely unnecessary to blindly kill it, anyways I'll never understand how you can be so reckless with your phone..
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Edit: the state you brought your phone into is called "hard bricked" - have fun..
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Aight thank you i had some suspicion it might be ...-bricked didnt know which though so thank you
If you can get in the bootloader then possibly the device is still OK. Just need to get the right ROM.
Try different TWRP versions. Sometimes, one particular version can save the world.
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken
There are few different versions of P9 Lite, look at the back of the phone to the bottom to see the numbers beside VSN and let us know.
1) Also when the phone is turned off plug in the usb to a computer or charging adapter
2) Hold down volume up & power
3) Let go of the power button when you feel the buzz while still holding the volume up button
4) Download latest version & recovery.
5) Go to Settings>Developer Options>USB Debugging On
5B) If you don't see Developer Options in settings, then go to Settings>About Phone>Build Number & ( tap the Build Number untill it unlocks)
6) Update us on the status, hope it works out.
GloryNation said:
There are few different versions of P9 Lite, look at the back of the phone to the bottom to see the numbers beside VSN and let us know.
1) Also when the phone is turned off plug in the usb to a computer or charging adapter
2) Hold down volume up & power
3) Let go of the power button when you feel the buzz while still holding the volume up button
4) Download latest version & recovery.
5) Go to Settings>Developer Options>USB Debugging On
5B) If you don't see Developer Options in settings, then go to Settings>About Phone>Build Number & ( tap the Build Number untill it unlocks)
6) Update us on the status, hope it works out.
Click to expand...
Click to collapse
tried to enter recovery, still not work. can't go to developer options because phone is stuck on logo, can't power off. couldn't find any solution that works anywhere, been searching for more than 6 hours, still no use. phone model is VNS-L21 forgot to mention earlier
What exactly were you doing before this happened and does your computer recognize your phone when plugged in at all.
Try holding volume up & down together & plug phone in when it reboots on you, & report back with what you see. If anything at all.
GloryNation said:
What exactly were you doing before this happened and does your computer recognize your phone when plugged in at all.
Try holding volume up & down together & plug phone in when it reboots on you, & report back with what you see. If anything at all.
Click to expand...
Click to collapse
I tried to install nougat update, computer recognizes it only in fastboot. holding volume buttons haven't changed anything still no progress. the thing is i had installed nougat a moth or so ago and it worked fine, then rolled back to marshmallow and now this. i'm pretty sure i tried to install correct package, because it was the same i had installed earlier
Did you download a adb tool on your computer that have the 'fastboot.exe' file? If so open that folder,
Have the mouse curser hover in that folder, hold down shift & right click the mouse
Open command prompt
Connect phone as is in fastboot mode
Type adb devices & press enter
Type adb continue & press enter
Hi,
I have the same issue as ellanyx.
my phone can only be stucked while booting or if I connect my phone to a computer, I'm able to boot it in fastboot.
as ellanyx, I didn't enable usb-debug nor OEM unlock option...
so when I'm in fastboot, I type the command "fastboot oem unlock xxxxxx" (hopefully the different data needed are the correct ones mentioned on the box of the phone) I get this error message:
C:\Users\Dieu\Downloads\SRKToolHuawei-STABLE-V1.3-20160619>fastboot oem unlock xxxxx
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
and off course the other options like "fastboot flash recovery recovery.img "... doesn't work.
I can't use the adb commands neither.
when I type the commande, as mentioned above, "adb devices" or "adb continue", nothing works.
So I'm a bit desesperate
do you have any solution for this kind of issue?
thanks
Dude, so the last firmware on your phone was MM or N? If it was MM you should put stock firmware appropriate for your model in dload folder on SD card and put volume+volume-power, and thats it. If you stack on N,....then I dont know because dload method doesnt work with N, or maybe works if you can find stock firmware with recovery for N.
Regards
Unfortunately I can't update with the 3 button update otherwise it would indeed solvemy problem.
pyromana said:
Unfortunately I can't update with the 3 button update otherwise it would indeed solvemy problem.
Click to expand...
Click to collapse
Probably you didnt have correct Oeminfo for MM if dload method didnt work....Try to conect phone with Toolkit and follow procedure for flashing oeminfo and custombin, after that flash stock recovrry and b161 via dload metod. You will find it on forum here.
Regards
the procedure from SRK toolkit?
would it be possible to provide it? because I can't unlock the OEM and I didn't tick the USB debug think.
Maybe problem with the ps not phone so u can not connect with adb
Try with different pc you must have flash oem with fast boot without enable adb from phone if u in fastboot
I can only boot my phone in fastboot (vol- + power) and not in recovery (vol+ + power).
also when using the SRK toolkit, the first screen tells me to be sure that the usb debugging is enable, which I haven't done...
if I'm not mistaken, fastboot is to use the fastboot command and recovery the adb commands
the connection with fastboot works on my computer, the link is made. however when I type the command to unlock the OEM, I get an error stating that the command is not allowed.
when I use the SRK toolkit, with the different questions, he tries to connect the phone with adb and waiting.... waiting...
is there a command to reboot in recovery but from fastboot? in the otherway around it exists but it doesn't seem that from fastboot to recovery it exists.
thanks.
Alexxxx1 said:
Dude, so the last firmware on your phone was MM or N? If it was MM you should put stock firmware appropriate for your model in dload folder on SD card and put volume+volume-power, and thats it. If you stack on N,....then I dont know because dload method doesnt work with N, or maybe works if you can find stock firmware with recovery for N.
Regards
Click to expand...
Click to collapse
dload method works on N. I downgraded my phone from unofficial N update back to official MM update using this method yesterday. You just have to enable OEM at developer options on settings.
It looks like people can't be bothered to read the 1st post properly before they reply.
HE CAN NOT BOOT TO ANDROID SO HE CAN NOT ENABLE OEM OR ACTIVATE USB DEBUGGING!!!!
What he CAN do, is go into eRecovery and Fastboot.
With that in mind, I would suggest using the dload method through fastboot.
Also, make sure it is Huawei SRK Tools 2.0 that is used, as it actually asks if you are in debug mode or fastboot.
Note that there is a few bugs in SRK 2.0:
The TWRP recovery file has the wrong filename in the package, so it WILL fail unless you name it correctly.
Also, when trying to root, do NOT use the "P9 Lite" method as that WILL fail too. Use the "P9/P9 Plus" method.
I am trying to set up a complete guide that can restore the phone when it is stuck in fastboot, however I apparently went a step too far...
ellanyx said:
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken[/QUOTE
Do you have TWRP recovery ?
---------- Post added at 09:55 AM ---------- Previous post was at 09:50 AM ----------
ellanyx said:
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken
Click to expand...
Click to collapse
Boot into fastboot mode and flash a custom recovery by meticulus. Link : meticulus.co.vu
Then whenyou get stuck hold power and vol down button for 2 minutes the phone will reboot and then when it says that your device has been unlocked and cant be trusted then only press vol up key ( dont press power button then). The u get into huawei recovery. From that u should power off the phone. Now get a custom rom by meticulus into your device sd card ( Cyanogenmod 13 is recommended ). Then insert sd card in a powered off phone. Now press vol up and power key and flash gapps and custom rom and you are good to go.
Click to expand...
Click to collapse
So, MY question:
I have tried 4 times to get Nougat installed, but every time I got the SMALL package (1.25gb) which means it is not complete.
I decided to try ONE more time, but think I have made a serious mistake.
I was on B161 and tried to downgrade to B160 without upgrading to Nougat first.
This has caused my phone to be stuck at boot with the message "Your device is booting now..."
I can NOT get into eRecovery or fastboot no matter what I do.
If I just leave the phone, then it discharge very fast, but as soon as I plug it in, it starts up and gets stuck at the same screen again.
Does anyone have ANY idea about how I can get out of this problem?
UPDATE:
I have managed to boot to fastboot while connected to my pc.
The phone is unlocked but FRP is LOCKED, which means I can't flash anything.
I read about using Miracle Loader to remove the FRP lock, but it can't "see" my phone. Maybe I am doing it wrong?
SnowmanDK said:
So, MY question:
I have tried 4 times to get Nougat installed, but every time I got the SMALL package (1.25gb) which means it is not complete.
I decided to try ONE more time, but think I have made a serious mistake.
I was on B161 and tried to downgrade to B160 without upgrading to Nougat first.
This has caused my phone to be stuck at boot with the message "Your device is booting now..."
I can NOT get into eRecovery or fastboot no matter what I do.
If I just leave the phone, then it discharge very fast, but as soon as I plug it in, it starts up and gets stuck at the same screen again.
Does anyone have ANY idea about how I can get out of this problem?
UPDATE:
I have managed to boot to fastboot while connected to my pc.
The phone is unlocked but FRP is LOCKED, which means I can't flash anything.
I read about using Miracle Loader to remove the FRP lock, but it can't "see" my phone. Maybe I am doing it wrong?
Click to expand...
Click to collapse
Try to relock and then unlock the bootloader again. And make sure oem unlocking is enabled in dev options
Arsaam said:
Try to relock and then unlock the bootloader again. And make sure oem unlocking is enabled in dev options
Click to expand...
Click to collapse
Please read my previous post again
I can NOT boot normally. And as FRP is locked, then I can't relock or unlock the bootloader.
SnowmanDK said:
Please read my previous post again
I can NOT boot normally. And as FRP is locked, then I can't relock or unlock the bootloader.
Click to expand...
Click to collapse
Go to fast boot mode and from their try to flash meticulus recovery.
You can also try the adb method as well.
Visit meticulus.co.vu
I will try to explain everything from the beginning. I was about to install a custom rom install (it was in 7.1.1 stock, unlocked bootloader) so when I was going to do full wipe with lastest TWRP there was an error. Wait for about 15 minutes just in case, but nothing happened so I decided to restart it to try again. But the phone stuck in the ZTE logo and if it tried to enter TWRP was stuck in the logo too, I tried with all versions of TWRP and no one works. Find a post that said I could use TWRP tenfars tool to recover my phone and had to enter the EDL mode. I managed to put the phone in edl mode but now I can not get out of it. I press and hold the power button for a minute and nothing happens (no vibration, no led, no ZTE logo) my pc just does the unplug windows sound. My pc recognizes the phone as QUSB_BULK. When I try to use the tenfars tool I get this message:
C:\Users\Alejandro Saavedra\Downloads\minimal_adb_fastboot_1.4.1_portable>axon7tool -w recovery
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Also try using the xiaomi MiFlash tool (even change the drivers from QUSB_BULK to COM COM 5) but something similar happens, also tells me can not recive hello package.
I'm a little new to this so I beg you a little patience
Please work very hard to buy this phone, there has to be some way to unbrick it. :crying:
If you need any additional information just tell me
If you use axon7tool :
check in Devices Manager if is called QLIBSD.
rename recovery.img to recovery.bin.
If you use MiFlash :
get latest version : https://www.androidfilehost.com/?fid=673368273298954241
check in Devices Manager if is called Qualcomm 8004.
CelesteBlue said:
check in Devices Manager if is called QLIBSD.
rename recovery.img to recovery.bin.
Click to expand...
Click to collapse
You need two files, recovery.img and recovery.bin in same folder. (Don't forget to unzip tenfars TWRP and after that rename and make a copy)
Please read: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Best regards
Smedslund
Smedslund said:
You need two files, recovery.img and recovery.bin in same folder. (Don't forget to unzip tenfars TWRP and after that rename and make a copy)
Please read: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Best regards
Smedslund
Click to expand...
Click to collapse
anyway :
https://ab-exclusive.us/fileserver/uploads/twrp_rec_tenfar.zip
404 Not Found...
To flash a recovery file (STOCK or TWRP) with axon7tool, the file has to be called recovery.bin.
CelesteBlue said:
anyway :
https://ab-exclusive.us/fileserver/uploads/twrp_rec_tenfar.zip
404 Not Found...
To flash a recovery file (STOCK or TWRP) with axon7tool, the file has to be called recovery.bin.
Click to expand...
Click to collapse
You will find tenfar 3.0.2-2 TWRP at download center:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Once unzipped, copy it to recovery.bin:
copy twrp_rec_tenfar.img recovery.bin
Thanks to everyone for your answers, I was able to recover my phone using miflash, qualcom usb drivers and this ROM https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip I put my phone in EDL mode and then flash the mentioned rom. It took me like 20-30 tries to finally get it. The last attempt I made was to unplug the device from the computer, I kept the power button for 10 seconds and connect it to the computer without ever releasing the power button. It was seen as always (black screen, not led) but for some reason this time works. I hope everyone can solve this problem. Can pm me if you need help, maybe i can help with something
ale0796 said:
Thanks to everyone for your answers, I was able to recover my phone using miflash, qualcom usb drivers and this ROM https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip I put my phone in EDL mode and then flash the mentioned rom. It took me like 20-30 tries to finally get it. The last attempt I made was to unplug the device from the computer, I kept the power button for 10 seconds and connect it to the computer without ever releasing the power button. It was seen as always (black screen, not led) but for some reason this time works. I hope everyone can solve this problem. Can pm me if you need help, maybe i can help with something
Click to expand...
Click to collapse
That's because you reset the EDL that way. the method is weird but seemed to work...
If you hold the 3 buttons for ~10 secs while the device is in EDL it will reset it
@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.
CelesteBlue said:
@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.
Click to expand...
Click to collapse
Actually, it is a nice feature for the few seconds it lasts, but read HERE if you must. Be careful!
Good luck
CelesteBlue said:
@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.
Click to expand...
Click to collapse
I'd advice against doing it... I had no trouble with it but a bunch of people now have paperweights. But yeah, the link is the one provided by the other guy above me
Thank you so much @Choose an username... and @amphi66 : that worked !
Anyway I am on G B04 (Nougat).
Do you know some cool mods I should do ?
Like debloat, remove the boot message (done), etc...
Hi everyone, i have a big problem. Today i was trying to help a firend of mine by unlocking his bootloader on this phone but i got a strange message when i was trying to boot in Download mode. The message was:
"fastboot init( )
loading keystore failed status 5 usb init ept @ 0x8f20700
udc_start( )
fastboot: processing commands"
Basically it doesn't allowed me to enter in Download mode, so no reverting to v10f software, no pushing aboot, no twrp and no Marshmallow zip. Nothing at all, i could do nothing. In the following lines i will tell you what i did and tried:
1) Using different PC usb ports, no way to make it work
2) Using different cables, no way to make it work
3) Trying to boot in Download mode by removing battery and try without it, desperate, obviously no way to make it work
I spent two hours trying to find a way to make it work but i failed miserably...so i'm here hoping someone better than me can help me.
NOTES:
The phone was on original Lollipop firmware v10e (Italy) but rooted.
Basically i did nothing, just tried to put it in download mode (Vol - and plug usb in), tried also other ways but nothing showed up
When the phone is connected to pc (when it's on) it charges only, don't show the option to use mtp so... i think adb won't work
Hope it can help and hope you can help! XD
I had same error, cause of flashing the wron zip basically i needed to get into repair mode and use adb while its trying to repair use adb commands to reboot to recovery
Sent from my LG-H440 using Tapatalk
MadjijaHacker said:
I had same error, cause of flashing the wron zip basically i needed to get into repair mode and use adb while its trying to repair use adb commands to reboot to recovery
Sent from my LG-H440 using Tapatalk
Click to expand...
Click to collapse
But i need Download mode, not recovery. With adb i can access it?
P.S i didn't flash anything
Well, that's what helped me, i don't know was that helpful, you can still try repair mode
Giuskiller said:
But i need Download mode, not recovery. With adb i can access it?
P.S i didn't flash anything
Click to expand...
Click to collapse
Sent from my LG-H440 using Tapatalk
Giuskiller said:
Hi everyone, i have a big problem. Today i was trying to help a firend of mine by unlocking his bootloader on this phone but i got a strange message when i was trying to boot in Download mode. The message was:
"fastboot init( )
loading keystore failed status 5 usb init ept @ 0x8f20700
udc_start( )
fastboot: processing commands"
...
NOTES:
The phone was on original Lollipop firmware v10e (Italy) but rooted.
Basically i did nothing, just tried to put it in download mode (Vol - and plug usb in), tried also other ways but nothing showed up
...
Hope it can help and hope you can help! XD
Click to expand...
Click to collapse
Upload mode is phone off, press VOL+ and then plug the USB.
---------- Post added at 04:57 PM ---------- Previous post was at 04:55 PM ----------
MadjijaHacker said:
I had same error, cause of flashing the wron zip basically i needed to get into repair mode and use adb while its trying to repair use adb commands to reboot to recovery
Sent from my LG-H440 using Tapatalk
Click to expand...
Click to collapse
Can you give more details? How can I access that repair mode and how to use adb commands on it? I have a bricked board that I want to put back on use.
jorlando said:
Upload mode is phone off, press VOL+ and then plug the USB
Click to expand...
Click to collapse
Hi, i tried vol + but the phone just boots... i will try again and let you know in the evening
When device is off hold Vol- and power key until LG logo appear, then release the keys and hold them again, its really hard to time it correctly, but if you do you will get a factory reset option, on that screen you navigate using Vol+ and - buttons and power button is ok
Sent from my LG-H440 using Tapatalk
MadjijaHacker said:
When device is off hold Vol- and power key until LG logo appear, then release the keys and hold them again, its really hard to time it correctly, but if you do you will get a factory reset option, on that screen you navigate using Vol+ and - buttons and power button is ok
Sent from my LG-H440 using Tapatalk
Click to expand...
Click to collapse
Thank you, after the factory reset the combination Vol+ and USB worked (after a few try) and i was able to boot in Download mode, then i flashev v10f, rooted and pushed modified aboot, flashed twrp 1.1.0 with flashify (twrp official app failed many times) and finally installed v20b and supersu. Everything works as expected =)
Giuskiller said:
Thank you, after the factory reset the combination Vol+ and USB worked (after a few try) and i was able to boot in Download mode, then i flashev v10f, rooted and pushed modified aboot, flashed twrp 1.1.0 with flashify (twrp official app failed many times) and finally installed v20b and supersu. Everything works as expected =)
Click to expand...
Click to collapse
I am glad i could help [emoji2]
Sent from my LG-H440 using Tapatalk
oh man same problem if u fix this let me now how plzzzzzzz
Silentsx1 said:
oh man same problem if u fix this let me now how plzzzzzzz
Click to expand...
Click to collapse
Is there anything you can do on your phone or is it completely dead ?
I can enter the hardrester but itis not helping and in fastboot itis saying FAILED (remote: unknown command)
Silentsx1 said:
I can enter the hardrester but itis not helping and in fastboot itis saying FAILED (remote: unknown command)
Click to expand...
Click to collapse
Try to boot into download mode, if you can. Turn off your device then press and hold vol. Up and plug in the cable.
i cant turn off my device legit after i put battery fastboot show up :crying::crying::crying::crying:
Silentsx1 said:
i cant turn off my device legit after i put battery fastboot show up :crying::crying::crying::crying:
Click to expand...
Click to collapse
Can you post a screenshot here ?
here i cant do anything plz help
https://ibb.co/kmZCmG
https://ibb.co/eMB3tw
https://ibb.co/mQsMfb
https://ibb.co/dpf7Lb
Silentsx1 said:
here i cant do anything plz help
https://ibb.co/kmZCmG
https://ibb.co/eMB3tw
https://ibb.co/mQsMfb
https://ibb.co/dpf7Lb
Click to expand...
Click to collapse
Do you have twrp installed on your phone ? If, yes try to boot into it.
I have a similar problem with my LG Spirit. When it tries to boot, it shows an error message: Boot Verification Fail, DIFFERENT_HASH... After that it just restarts endlessly... I can't enter download mode, because the computer doesn't recognize it when I plug it in via usb cable... The only thing I can do is to get to the hard reset screen, but that is useless because it just restarts and shows the same error mentioned above... I'm out of ideas, the only thing that comes to my mind is to try and see if Ubuntu recognizes it, but then again, there's no LG Flash Tool made for Linux, or is there?
Sorry for mistakes, english is not my native language.
Hrastostit said:
I have a similar problem with my LG Spirit. When it tries to boot, it shows an error message: Boot Verification Fail, DIFFERENT_HASH... After that it just restarts endlessly... I can't enter download mode, because the computer doesn't recognize it when I plug it in via usb cable... The only thing I can do is to get to the hard reset screen, but that is useless because it just restarts and shows the same error mentioned above... I'm out of ideas, the only thing that comes to my mind is to try and see if Ubuntu recognizes it, but then again, there's no LG Flash Tool made for Linux, or is there?
Sorry for mistakes, english is not my native language.
Click to expand...
Click to collapse
If your pc doesn't recognise it, try to find an another computer that you can try it on .
mayankjet said:
If your pc doesn't recognise it, try to find an another computer that you can try it on .
Click to expand...
Click to collapse
Thank's for your reply. I did just that, but without success... I also tried to do what MadjijaHacker wrote, but I can't get it right. I mean, I can enter in hard reset, but can't get to download mode. It seems that my phone is dead...
I messed up
quick history:
I tried to install OREO using this guide. I debranded to Al10 and installed OREO, but google apps were not working so I tried to roll back. I used the SRK tool to debrand back to L29C185, and then used this nougat roll back package from here (using dload method). The dload update completed but after reboot I was getting the "Error mode" message. At this point I had access to fastboot but couldn't run any command and I would get:
FAILED (remote: Command not allowed)
I read other threads and tried to re-unlock the bootloader. I did that and the unlock oem command worked, but now I got stuck at Error mode and I can't even access the fastboot mode :'(
The current error page screenshot is attached.
Please tell me there is a way to fix this ='[
copycat1819 said:
I messed up
quick history:
I tried to install OREO using this guide. I debranded to Al10 and installed OREO, but google apps were not working so I tried to roll back. I used the SRK tool to debrand back to L29C185, and then used this nougat roll back package from here (using dload method). The dload update completed but after reboot I was getting the "Error mode" message. At this point I had access to fastboot but couldn't run any command and I would get:
FAILED (remote: Command not allowed)
I read other threads and tried to re-unlock the bootloader. I did that and the unlock oem command worked, but now I got stuck at Error mode and I can't even access the fastboot mode :'(
The current error page screenshot is attached.
Please tell me there is a way to fix this ='[
Click to expand...
Click to collapse
So you rebranded back to L29C185...
So you followed a downgrade to marshmallow guide: https://forum.xda-developers.com/ma...-emui-5-to-t3515202/post69986527#post69986527
And decided to stop at step 5 after using a only 100MB dload to downgrade from oreo to nougat...
And then decided to your lock bootloader
I would advise to use dload mode now to install a working nougat dload archive for L29C185.
---------- Post added at 18:33 ---------- Previous post was at 18:27 ----------
oslo83 said:
So you rebranded back to L29C185...
I would advise to use dload mode now to install a working nougat dload archive for L29C185.
Click to expand...
Click to collapse
Use that free one:
https://androidhost.ru/3m5
It should install fine and restore fully your device.
oslo83 said:
So you rebranded back to L29C185...
So you followed a downgrade to marshmallow guide: https://forum.xda-developers.com/ma...-emui-5-to-t3515202/post69986527#post69986527
And decided to stop at step 5 after using a only 100MB dload to downgrade from oreo to nougat...
And then decided to your lock bootloader
I would advise to use dload mode now to install a working nougat dload archive for L29C185.
---------- Post added at 18:33 ---------- Previous post was at 18:27 ----------
Use that free one:
https://androidhost.ru/3m5
It should install fine and restore fully your device.
Click to expand...
Click to collapse
Thank you for your prompt reply. The thing is the phone is now in boot loop of that "Error mode" screen shot. I hold vol + and - as soon as it resets but the recovery (for installing dload) won't show up and again the "error mode" page shows up. Do you think this can be fixed if I wait for the battery to drain and phone shuts down?
Thanks again,
copycat1819 said:
Thank you for your prompt reply. The thing is the phone is now in boot loop of that "Error mode" screen shot. I hold vol + and - as soon as it resets but the recovery (for installing dload) won't show up and again the "error mode" page shows up.
Do you think this can be fixed if I wait for the battery to drain and phone shuts down?
Thanks again,
Click to expand...
Click to collapse
Try again with no usb cable plugged in and with a sd or USB-OTG exfat formatted.
Battery drain, you'll see...
oslo83 said:
Try again with no usb cable plugged in and with a sd or USB-OTG exfat formatted.
Battery drain, you'll see...
Click to expand...
Click to collapse
I tried unzipped the ROM and put it in dload folder of the sd card (I had used the same sd card with dload method several times).
Holding down vol+ and - doesn't do anything and doesn't run the recovery. The whole thing is just a boot loop of that screen shot.
What do you mean by "battery drain ... you'll see" ? Should I let the battery die before trying that? the battery is not drained yet.
How is shown device in windows device manager when plugged to computer?
'USBSer' ?
oslo83 said:
How is shown device in windows device manager when plugged to computer?
'USBSer' ?
Click to expand...
Click to collapse
In this "error mode" boot loop nothing is shown in the windows device manager. Also there is no plug and play sound , as if USB is not connected at all. Probably because it is not in fastboot mode, right?
oslo83 said:
How is shown device in windows device manager when plugged to computer?
'USBSer' ?
Click to expand...
Click to collapse
The battery just drained and I tried the fastboot mode but the fastboot page doesn't show up. Only the same "Error Mode" page shows up
Huawei service care ?
Or open phone, use testpoint:
https://easy-firmware.com/media/articles/large/2018/08/17/237829-1534544261.jpg
and use a paying timed license to flash a working firmware with DC/HCU/HDE... Tools.
oslo83 said:
Huawei service care ?
Or open phone, use testpoint:
https://easy-firmware.com/media/articles/large/2018/08/17/237829-1534544261.jpg
and use a paying timed license to flash a working firmware with DC/HCU/HDE... Tools.
Click to expand...
Click to collapse
For any one who ended up visiting this thread I actually had to do what oslo suggested. This is the method 3 of DC-unlocker. Paid for a 3-day license of dc-unlocker and HCU and then used the testpoint method to fix the phone. Two points:
- when you are doing that in windows 10, you have to disable the driver signature enforcement to be able to install install the Huawei com driver.
- The test point is just one point, meaning that the other point is the ground (practically most of those silver metals beside the test points are all ground)
Hi guys, I messed up my mate 8 64gb variant. C636. Im not sure exactly what has happened with the phone but I'll explain. I updated to nougat, unlocked bootloader and then completely forgot that with nougat..you can't root the same way as with mm. Now all I get is the your device is unlocked and cant be trusted msg....and that's it!.
What exactly has happened? Vol up + down +power doesn't work and I have no erecovery.
What's the best way to fix this?
Sent from my AL10
ubermorgan said:
Hi guys, I messed up my mate 8 64gb variant. C636. Im not sure exactly what has happened with the phone but I'll explain. I updated to nougat, unlocked bootloader and then completely forgot that with nougat..you can't root the same way as with mm. Now all I get is the your device is unlocked and cant be trusted msg....and that's it!.
What exactly has happened? Vol up + down +power doesn't work and I have no erecovery.
What's the best way to fix this?
Sent from my AL10
Click to expand...
Click to collapse
Try dload method. Create dload folder in sd card, then from nougat zip rom extract UPDATE.APP and place in the folder. With phone off press and hold Vol up + down +power.