Related
I recently tried to flash PureNexus rom from chroma rom.... I know I did a clean install because it was successful but when I hit wipe davik it got stuck on the boot screen. When I restarted it apparently wiped my internal storage. Now I get this message "Your device is corrupt. It can't be trusted and may not work properly."
The device is now LOCKED and NULLED... adb reboot bootloader does not work....
Cant flash images
CANT UNLOCK
When I try to unlock it "fastboot flashing unlock" i get this message "FAILED (remote: device is locked. Cannot flash images)"
I can't go into the device and enable OEM cause there is no ROM to get into.
I can't drop files onto my device because it's not recognized by my device.... BUT ANDROID ADB INTERFACE shows up under device manager.
ANY HELP IS APPRECIATED?
I think you were on the wrong vendor which caused this so you can't get to the boot loader? Did try doing it manually not via adb
blacky305 said:
I recently tried to flash PureNexus rom from chroma rom.... I know I did a clean install because it was successful but when I hit wipe davik it got stuck on the boot screen. When I restarted it apparently wiped my internal storage. Now I get this message "Your device is corrupt. It can't be trusted and may not work properly."
The device is now LOCKED and NULLED... adb reboot bootloader does not work....
Cant flash images
CANT UNLOCK
When I try to unlock it "fastboot flashing unlock" i get this message "FAILED (remote: device is locked. Cannot flash images)"
I can't go into the device and enable OEM cause there is no ROM to get into.
I can't drop files onto my device because it's not recognized by my device.... BUT ANDROID ADB INTERFACE shows up under device manager.
ANY HELP IS APPRECIATED?
Click to expand...
Click to collapse
How did your bootloader get locked? That is something you have to intentionally do. And I know you must have unlocked it because you were using a custom recovery.
---------- Post added at 08:21 PM ---------- Previous post was at 08:16 PM ----------
This is right from Heisenbergs guide
Important: do not lock the bootloader unless you have first flashed the stock images. Locking the bootloader while you have a custom recovery installed can result in a brick. Please also note that the locking procedure will wipe all user data from the device.
Gizmoe said:
How did your bootloader get locked? That is something you have to intentionally do. And I know you must have unlocked it because you were using a custom recovery.
Click to expand...
Click to collapse
Ya, not sure how your internal storage getting deleted has anything to do with your bootloader getting locked.
YOU had to have locked your bootloader.
And as to why you did that, I have NO idea... And as of where to go from here? Also no idea.
Good luck man, that's a crappy situation, hope you get it fixed somehow
Hi,, I need help, don't now what to do, I run King root on my phone, xt1562, and **** up everything.... you can see in the pics.. I search, and I can find solution, so please somebody give me the solution for this problem. I tray with adb, mfasboot, rds life to refresh on lollipop without results.
Not sure if i understand your problem, but have you tried to flash twrp to be able to boot in recovery and then flash a rom
you need to unlock your device first then flash twrp recovery , and install supersu to root the device.
try this: http://forum.xda-developers.com/moto-x-play/general/untested-how-to-root-moto-x-play-t3211941
I tray that, but don't work for me, before I start with King root I alow OEM unlock on the developer settings on the phone, and now Adb don't recognize that and ask for OEM unlock, and it impossible now cos phone don't work
lapena said:
I tray that, but don't work for me, before I start with King root I alow OEM unlock on the developer settings on the phone, and now Adb don't recognize that and ask for OEM unlock, and it impossible now cos phone don't work
Click to expand...
Click to collapse
Flash factory firmware, it's pretty much the only thing you can do with locked bootloader. And don't use kingroot any more
minimale_ldz said:
Flash factory firmware, it's pretty much the only thing you can do with locked bootloader. And don't use kingroot any more
Click to expand...
Click to collapse
I try that last 7days with no success, that's why I'm posting this, if you now some link that will be great. Tnx
lapena said:
I try that last 7days with no success, that's why I'm posting this, if you now some link that will be great. Tnx
Click to expand...
Click to collapse
Did you originally have Lollipop or MM. Here's MM firmware:
If it's european XT1562, single sim, try this one:
http://www.filefactory.com/file/1ub...MPD24.107-52_cid7_subsidy-DEFAULT_CFC.xml.zip
If it's asian, dual sim, this one:
http://www.filefactory.com/file/49g...MPD24.107-70_cid7_subsidy-DEFAULT_CFC.xml.zip
(double check it, for you own safety)
Make sure you've got moto drivers and use fastboot or mfastboot.
What messages did you get when flashing before, what did it say exactly after executing fastboot commands?
Tnx
Before, phone was originally on lollipop, and receive Ota update on MM6. 0.1.
I tried to root this phone through this bull**** Kingroot.. And it failed.. Later on when i restarted the phone it got bootlooped and is totally bricked! i get this error- Startup Failed: Your device didn't start up successfully. use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant.
AP Fastboot flashmode (secure)
Fastboot Reason: Last time flashing failed
hab check failed for boot
failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation. backup to fastboot
Boot Up failed
I try with fastboot, and rds lite, computer show connection like adb devices, but when I try to flash, said failed, and rds don't show anethyng, don't recognize phone.
lapena said:
Before, phone was originally on lollipop, and receive Ota update on MM6. 0.1.
I tried to root this phone through this bull**** Kingroot.. And it failed.. Later on when i restarted the phone it got bootlooped and is totally bricked! i get this error- Startup Failed: Your device didn't start up successfully. use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant.
AP Fastboot flashmode (secure)
Fastboot Reason: Last time flashing failed
hab check failed for boot
failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation. backup to fastboot
Boot Up failed
I try with fastboot, and rds lite, computer show connection like adb devices, but when I try to flash, said failed, and rds don't show anethyng, don't recognize phone.
Click to expand...
Click to collapse
If you installed MM OTA you can't flash Lollipop firmware, it must be MM (generally speaking). Get into bootloader and try to flash MM with fastboot.
minimale_ldz said:
If you installed MM OTA you can't flash Lollipop firmware, it must be MM (generally speaking). Get into bootloader and try to flash MM with fastboot.[/QUOTE
Thats the problem..look at adeded pictures in first post...
Click to expand...
Click to collapse
lapena said:
Hi,, I need help, don't now what to do, I run King root on my phone, xt1562, and **** up everything.... you can see in the pics.. I search, and I can find solution, so please somebody give me the solution for this problem. I tray with adb, mfasboot, rds life to refresh on lollipop without results.
Click to expand...
Click to collapse
Check this out, this guy had the same problem and report here if it worked, it'll help others.
http://forum.xda-developers.com/showpost.php?p=68813881&postcount=43
lapena said:
minimale_ldz said:
If you installed MM OTA you can't flash Lollipop firmware, it must be MM (generally speaking). Get into bootloader and try to flash MM with fastboot.[/QUOTE
Thats the problem..look at adeded pictures in first post...
Click to expand...
Click to collapse
I can see it boots in fastboot mode, which is good, but your firmware is messed. Is your phone sim-free or carrier branded? If it's sim-free you should be able to flash the firmware I linked.
Click to expand...
Click to collapse
Tnx
Yes it's Sim free xt1562, model SM4232AD1T1, belive me I try everything, adb, or rds, or mfasboot., don't recognize device, in device list on comp. It's listed something like Fastbot lux... Windows 7.
Tnx, one more time for you will to help.
lapena said:
Yes it's Sim free xt1562, model SM4232AD1T1, belive me I try everything, adb, or rds, or mfasboot., don't recognize device, in device list on comp. It's listed something like Fastbot lux... Windows 7.
Tnx, one more time for you will to help.
Click to expand...
Click to collapse
OK, I guess you installed drivers for it, but maybe reinstall. They're here:
https://motorola-mobility-en-xp.custhelp.com/app/answers/detail/a_id/89880
Can you tell what exactly it says when you enter
Code:
fastboot devices
in command window?
Tnx
When I type that command just display some numbers... Am not at home now, so I can't post number
lapena said:
When I type that command just display some numbers... Am not at home now, so I can't post number
Click to expand...
Click to collapse
if it displays something like this:
Code:
30D41467 FASTBOOT
Then I guess you're good to go with flashing firmware
That's number and text what I got on display, but when I tray next kommand, Fastbot failed.. What to do...for example I typed command fastbot OEM fb_mode_set. On display have this line
(bootloader) slot-count:notfound
(bootloader) slot-suffix:not found
(bootloader) slot-suffix:not found
FAED(remote failure)
lapena said:
That's number and text what I got on display, but when I tray next kommand, Fastbot failed.. What to do...
Click to expand...
Click to collapse
what's the next command you try?
---------- Post added at 20:44 ---------- Previous post was at 20:32 ----------
lapena said:
That's number and text what I got on display, but when I tray next kommand, Fastbot failed.. What to do...for example I typed command fastbot OEM fb_mode_set. On display have this line
(bootloader) slot-count:notfound
(bootloader) slot-suffix:not found
(bootloader) slot-suffix:not found
FAED(remote failure)
Click to expand...
Click to collapse
Did you try to skip this one and start with flashing gpt.bin and then just do the minimum, like here:
http://forum.xda-developers.com/showpost.php?p=62708260&postcount=5
(you may have more sparsechunks to flash, so check their number)
Tnx
Of course I am, and same thing happened... I'm going crazy...
lapena said:
Of course I am, and same thing happened... I'm going crazy...
Click to expand...
Click to collapse
Did you try to skip first 2 commands (gpt and bootloader) and start from
Code:
fastboot flash logo logo.bin
?
So I upgraded to Nougat on my P9 Lite, unlocked boot loader, used twrp, flashed roms and everything went smooth. Saw a more up-to-date version with no bugs, so I had to downgrade to MM first.
I followed a guide, but I messed up somewhere and ended up having my bootloader locked, and I can't access the OS to enable developer options and oem unlock from settings. The reason why I can't access the OS is that I am stuck in the setup. I am stuck at the part where I have to sign in to my google account. It doesn't show a keyboard, only a microphone, and I can't use that for my password (it won't let me).
Any ideas?
TL;DR messed up during downgrading from Nougat to MM, now TWLR is gone, bootloader is locked and my main issue is that when I get to the google account sign in part during OS setup, there is no keyboard (I can only use dictation) so I can't sign in... So I'm stuck
Also, can I unlock bootloader without access to OS, without being able to navigate to settings, enable developer options and then oem unlock?
1. Stuck in OS setup? Signing in to Google? Hey, it's not obligatory, can't you just skip it?
2. Flashing ROMS locked your bootloader, it's normal, but I'm sure it didn't change the "oem unlock" setting you had surely enabled before. Go to fastboot mode and check Bootloader and FRP status on the bottom of the screen. If FRP is unlocked, you will be able to unlock bootloader again.
3. If you have your TWRP gone (flashed by stock ROM), flash the recovery partition manually - fastboot flash recovery TWRP.img (download from Meticulus Project site).
Jagiel88 said:
1. Stuck in OS setup? Signing in to Google? Hey, it's not obligatory, can't you just skip it?
2. Flashing ROMS locked your bootloader, it's normal, but I'm sure it didn't change the "oem unlock" setting you had surely enabled before. Go to fastboot mode and check Bootloader and FRP status on the bottom of the screen. If FRP is unlocked, you will be able to unlock bootloader again.
3. If you have your TWRP gone (flashed by stock ROM), flash the recovery partition manually - fastboot flash recovery TWRP.img (download from Meticulus Project site).
Click to expand...
Click to collapse
It is obligatory, I couldn't skip it. I tried to use other methods of signing in, but then it asked me to reset password at the end.
Both Phone and FRP are locked
I think I have missed this, but I can't do it via fastboot because I keep getting "Command not allowed" whenever I try to unlock bootloader or do anything via fast boot.
Also, thank you so much for your time and input. It is much appreciated.
That's weird, I flashed my phone several times with different ROMS (not Nougat) and this setting (oem unlock / FRP unlocked) stayed enabled. Don't know where it sits then and how to change it without getting inside OS. But - what about TWRP? Oh right, you won't be able to flash it without unlocked bootloader... Oh, crap. I would try SRK Tool for Huawei to play with bootloader, it uses fastboot so shouldn't help, but maybe, just maybe? Maybe try flashing whole ROMs through dload folder on SD? Stock 120, 161, Nougat, I would try these. I hope there is some way to unlock FRP, probably it's possible in DC-unlocker (it's a paid software).
Jagiel88 said:
That's weird, I flashed my phone several times with different ROMS (not Nougat) and this setting (oem unlock / FRP unlocked) stayed enabled. Don't know where it sits then and how to change it without getting inside OS. But - what about TWRP? Oh right, you won't be able to flash it without unlocked bootloader... Oh, crap. I would try SRK Tool for Huawei to play with bootloader, it uses fastboot so shouldn't help, but maybe, just maybe? Maybe try flashing whole ROMs through dload folder on SD? Stock 120, 161, Nougat, I would try these. I hope there is some way to unlock FRP, probably it's possible in DC-unlocker (it's a paid software).
Click to expand...
Click to collapse
Yes, it's very weird. I haven't done the process a lot. But I've flashed a couple of phones I had before, went smooth. Nothing major like this happened before.
I will consider the SRK Tool and I did not know about the DC-Unlocker tool, thank you for telling me about it.
Flashing whole roms through dload folder only works with Nougat for some reason, and I keep getting stuck in the signing in problem because of no keyboard, someone told me that's incomplete software, I'm hoping that's the case, any ideas where can I get it from?
Again thank you Jagiel88 for your time and advice xD
No problem, unfortunately I haven't tried Nougat yet, so search for help on down/upgrade Nougat beta <-> Marshmallow threads .
youssefSamir said:
Yes, it's very weird. I haven't done the process a lot. But I've flashed a couple of phones I had before, went smooth. Nothing major like this happened before.
I will consider the SRK Tool and I did not know about the DC-Unlocker tool, thank you for telling me about it.
Flashing whole roms through dload folder only works with Nougat for some reason, and I keep getting stuck in the signing in problem because of no keyboard, someone told me that's incomplete software, I'm hoping that's the case, any ideas where can I get it from?
Again thank you Jagiel88 for your time and advice xD
Click to expand...
Click to collapse
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
islandman75 said:
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
Click to expand...
Click to collapse
There is 1 thing to unlock in settings . U have OEM lock
youssefSamir said:
Yes, it's very weird. I haven't done the process a lot. But I've flashed a couple of phones I had before, went smooth. Nothing major like this happened before.
I will consider the SRK Tool and I did not know about the DC-Unlocker tool, thank you for telling me about it.
Flashing whole roms through dload folder only works with Nougat for some reason, and I keep getting stuck in the signing in problem because of no keyboard, someone told me that's incomplete software, I'm hoping that's the case, any ideas where can I get it from?
Again thank you Jagiel88 for your time and advice xD
Click to expand...
Click to collapse
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
ScaleneVirus288 said:
There is 1 thing to unlock in settings . U have OEM lock
Click to expand...
Click to collapse
Can't access to any OS. I definetly know i had OEM unlocked, then after unlocking via fastboot, I wasn't able anymore to access the system.
islandman75 said:
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
Can't access to any OS. I definetly know i had OEM unlocked, then after unlocking via fastboot, I wasn't able anymore to access the system.
Click to expand...
Click to collapse
Unlock bootloader, after that you able to flash rom.
You use this command?
fastboot oem unlock YOUR_OEM_CODE
If you tip:
fastboot devices
What's you see?
I don't have an unlocked bootloader and i flashed the CWM. Now when i try to enter the recovery mode with buttons, nothing happens just turns the phone on normally. I searched for stock recoveries, but didn't found nothing.
I have GRA-L09, B200, Europe Open
Thanks for help!
To get an unlocked bootloader you must go to settings> about phone> build number
and then press build number 7 times
after you did that exit out of about phone then click on the newly-appeared 'developer settings'
there you should find OEM Unlocking and Enable USB Debugging
You'll get it from there.
I have the Dev Ops, but don't have OEM unlock.
But shouldn't you already have an unlocked bootloader to have DevOps?
Don't know. I don't typed any code in to unlock bootloader.
Are you sure you have DevOps?
---------- Post added at 01:58 PM ---------- Previous post was at 01:55 PM ----------
And also try to do it not with buttons, but with your computer
I don't know the script for how to boot into recovery mode but to fastboot, for example, you'd type in >fastboot
when your phone is connected to your PC via USB.
Y'know, just search up 'How to use Recovery Mode' - maybe you just did it wrong
Didn't tryed it w/ adb yet.
ADB didn't worked. I'm trying a full hard reset..
Hard reset didn't do nothing. HELP PLS!!
adb reboot-bootloader worked, but it has a subtitle: Phone Locked (with red). What is it?
TheGolem said:
adb reboot-bootloader worked, but it has a subtitle: Phone Locked (with red). What is it?
Click to expand...
Click to collapse
That means you have a locked bootloader, so CWM didn't install successfully.
In other words, you need to unlock the bootloader first in order to successfully install CWM.
So, 1st step - visit the Huawei unlocking code request page, taking your time to fill in the form accurately & submit it.
[Btw, if you don't already have a Huawei ID, you can register for one here: http://www-file.huawei.com/en/my-huawei/register
Then use these login details in the above link to request for the unlock code]
2nd step: Once you receive the unlock code from them, use it to unlock the bootloader by issuing the following command in fastboot mode [the asterisks (*) represent your 16-digit unlock code]:
Code:
fastboot oem unlock ****************
Now you can attempt to install CWM. Where are you getting the CWM img file from?
GaT7 said:
That means you have a locked bootloader, so CWM didn't install successfully.
In other words, you need to unlock the bootloader first in order to successfully install CWM.
So, 1st step - visit the Huawei unlocking code request page, taking your time to fill in the form accurately & submit it.
[Btw, if you don't already have a Huawei ID, you can register for one here: http://www-file.huawei.com/en/my-huawei/register
Then use these login details in the above link to request for the unlock code]
2nd step: Once you receive the unlock code from them, use it to unlock the bootloader by issuing the following command in fastboot mode [the asterisks (*) represent your 16-digit unlock code]:
Code:
fastboot oem unlock ****************
Now you can attempt to install CWM. Where are you getting the CWM img file from?
Click to expand...
Click to collapse
Sorry, "Phone Unlocked" with red
TheGolem said:
Sorry, "Phone Unlocked" with red
Click to expand...
Click to collapse
Ok, so it appears you may have corrupted the recovery partition.
Is the phone otherwise booting into the system & functioning normally?
Also, can you tell us what you are wanting to ultimately achieve by installing CWM?
Just to confirm the bootloader is unlocked, run this command in fastboot mode & let us know the result:
Code:
fastboot oem get-bootinfo
Ok, I just read your post in the other thread about wanting to update B200 to B370.
TheGolem said:
I have b200 but can't install it [B370]. Why?
Early flashed the CWM with flashify succesfully, but don't have unlocked bootloader. And if i try to enter recovery mode, nothing happens. Is it possible, that i cant' install it because of this?
Click to expand...
Click to collapse
As the guys already said, you do not need to install anything in order to update an official rom.
So, let's leave out CWM, bootloaders, etc for now, & help you update only from B200.
When you try using TopperBG's method to update, what happens?
What is your current FULL firmware version? It will be in this format: GRA-L09CxxxB200 - if everything else is as I've mentioned, I'm interested in the Cxxx part.
GaT7 said:
Ok, I just read your post in the other thread about wanting to update B200 to B370.
As the guys already said, you do not need to install anything in order to update an official rom.
So, let's leave out CWM, bootloaders, etc for now, & help you update only from B200.
When you try using TopperBG's method to update, what happens?
What is your current FULL firmware version? It will be in this format: GRA-L09CxxxB200 - if everything else is as I've mentioned, I'm interested in the Cxxx part.
Click to expand...
Click to collapse
Update succeed, it wroks fine. The problem is with the recovery mode.
When i'm trying the button method to enter recover, the phone just normally turns on. When still hold the buttons, black screen. It's with the abd too.
TheGolem said:
adb reboot-bootloader worked, but it has a subtitle: Phone Locked (with red). What is it?
Click to expand...
Click to collapse
you don't have a unlocked bootloader so you can't have cwm
I said it wrong:
-Android 5 succeed
-If i try to install Android 6
https://forum.xda-developers.com/huawei-p8/how-to/emui4-0-1-p8-official-marshmallow-6-0-t3417212
or enter recovery mode, then happens the black screen.
TheGolem said:
I said it wrong:
-Android 5 succeed
-If i try to install Android 6
https://forum.xda-developers.com/huawei-p8/how-to/emui4-0-1-p8-official-marshmallow-6-0-t3417212
or enter recovery mode, then happens the black screen.
Click to expand...
Click to collapse
1. You need to install stock recovery for android 5(unlocked bootloader is required).
2. Then you can use the dload method to update.
3. You can flash TWRP after that because no-one uses CWM.
GaT7 said:
Ok, so it appears you may have corrupted the recovery partition.
Is the phone otherwise booting into the system & functioning normally?
Also, can you tell us what you are wanting to ultimately achieve by installing CWM?
Just to confirm the bootloader is unlocked, run this command in fastboot mode & let us know the result:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
Phone normally booting, no problem with current system.
I typed in the command, and its <waiting for device>.
GaT7 said:
Where are you getting the CWM img file from?
Click to expand...
Click to collapse
http://www.teamandroid.com/2015/06/07/install-huawei-p8-clockworkmod-recovery/2/
Step 5
cwm-p8-nogui.img
I think i made i grave mistake. I want to upgrade my p9 lite to nougat so I decided to unroot my phone. The unrooting is successful with the device still booting. So next thing i want is to flash back my stock recovery so I can update my phone through OTA (this is where I made a mistake.) I tried doing it by flashing a full MM Rom that i got directly from huawei through dload method. The flashing went smoothly or so I thought. My phone got stuck in a boot loop and I cant seem to access recovery. eRecovery is also inaccessible so I tried reflashing the full MM Rom through dload method but I can't get it to work anymore. I tried it several times with no luck. I also tried reflashing meticulus' twrp through fastboot method but I always get an error saying "remote command not allowed". The bootloader is still unlock btw.
Someone help me. I don't know what to do anymore... :crying:
NikkoVicedo said:
I think i made i grave mistake. I want to upgrade my p9 lite to nougat so I decided to unroot my phone. The unrooting is successful with the device still booting. So next thing i want is to flash back my stock recovery so I can update my phone through OTA (this is where I made a mistake.) I tried doing it by flashing a full MM Rom that i got directly from huawei through dload method. The flashing went smoothly or so I thought. My phone got stuck in a boot loop and I cant seem to access recovery. eRecovery is also inaccessible so I tried reflashing the full MM Rom through dload method but I can't get it to work anymore. I tried it several times with no luck. I also tried reflashing meticulus' twrp through fastboot method but I always get an error saying "remote command not allowed". The bootloader is still unlock btw.
Someone help me. I don't know what to do anymore... :crying:
Click to expand...
Click to collapse
The bootloader appears unlocked, and says so, but it's not...I encountered the same situation with my colleagues device, you need to unlock it either way(careful this will wipe all your data if on nougat, but if on MM after unlocking keep phone connected to PC as it reboots and quickly press vol down+ power to get back to bootloader In order to flash TWRP, this will preserve your data partition and system), and try again, you need format that data partition by using changing format to f2fs then ext4...after this reboot, if it can't, reinstall the file In dload folder and go to stock recovery(disconnect phone from PC to do this if it fails) and do a factory reset.
.... if this fails, debrand And install MM or NOUGAT for your newly debranded system.
If this fails, which is highly unlikely,PM for un orthodox methods.
_New World Order (NWO)_
daner[email protected] said:
The bootloader appears unlocked, and says so, but it's not...I encountered the same situation with my colleagues device, you need to unlock it either way(careful this will wipe all your data if on nougat, but if on MM after unlocking keep phone connected to PC as it reboots and quickly press vol down+ power to get back to bootloader In order to flash TWRP, this will preserve your data partition and system), and try again, you need format that data partition by using changing format to f2fs then ext4...after this reboot, if it can't, reinstall the file In dload folder and go to stock recovery(disconnect phone from PC to do this if it fails) and do a factory reset.
.... if this fails, debrand And install MM or NOUGAT for your newly debranded system.
If this fails, which is highly unlikely,PM for un orthodox methods.
_New World Order (NWO)_
Click to expand...
Click to collapse
The problem is I cannot access recovery anymore. After trying to flash back full rom from huawei, i cannot access recovery anymore no matter how hard i try. eRecovery is also not accessible so i cannot turn off my phone. I tried flashing twrp trough fastboot i keep getting an error saying "remote command not allowed". Dload method is not working anymore. If only I can find a way to flash twrp, then I can restore the dump i made using meticulus' twrp.
NikkoVicedo said:
The problem is I cannot access recovery anymore. After trying to flash back full rom from huawei, i cannot access recovery anymore no matter how hard i try. eRecovery is also not accessible so i cannot turn off my phone. I tried flashing twrp trough fastboot i keep getting an error saying "remote command not allowed". Dload method is not working anymore. If only I can find a way to flash twrp, then I can restore the dump i made using meticulus' twrp.
Click to expand...
Click to collapse
Assuming that you have the unlock code, what happens if you try unlock bootloader again irrespective what status it is now?
_New World Order (NWO)_
[email protected] said:
Assuming that you have the unlock code, what happens if you try unlock bootloader again irrespective what status it is now?
_New World Order (NWO)_
Click to expand...
Click to collapse
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.
NikkoVicedo said:
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.
Click to expand...
Click to collapse
Hi guys, i Got the SAAAAAME Problem, this is all about what i PMd to you danerrickcuba FRP lock and bootloader unlocked. can't go to recovery, but has access to fastboot and wasn't able to do anything to fastboot.
Already fixed my phone. Had to pay 15 euros for DC Phoenix (this software saved me from bringing my phone to huawei service center to have it fix. Thank god!) so I can fix my phone. Recovery, eRecovery, Dload method working, and relocked bootloader. Currently updating my phone through OTA. Tnx danerrickcuba for suggesting methods to fix my phone....
NikkoVicedo said:
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.
Click to expand...
Click to collapse
i have the same problem
bootloader unlock and frp lock ,bootlooping,rec&e-rec destoryed
if you do not log out google /shut down "find my phone"/check oem-unlock in developer mode before downgrading or flashing ,you will get "frp lock" warning
bootlooping may come from wrong update.app. eg. i use dload method to flash rollback(5.0-B300) pkg in EMUI4.1 , my rec and e-rec are destoryed
however, i think fastboot command could do nothing to "bootloader unlock ,frp lock,rec and e-rec destoryed ". i do not know how DC-phoenix fix this and i pay a new motherboard for my mistake
try https://forum.xda-developers.com/showpost.php?p=71338813&postcount=29