Help with unlocking bootloader on the 626g+ - Desire 626 Q&A, Help & Troubleshooting

Basically "fastboot oem get_identifier_token" doesn't work, outputs
"FAILED (remote: unknown command)"
Flashing recovery doesn't work either "partition 'recovery' not support flash" but that's probably because the bootloader is still locked. I've rooted this phone with Kingoroot but not having a TWRP recovery bothers me a lot, since this device would most likely get bricked if factory resetted because Gapps were deleted. Also Kitkat is outdated for 2018.
Is there any possibility to get the identifier token, so as to unlock this bootloader on 626g+ dual sim version?

xdafanboii said:
Basically "fastboot oem get_identifier_token" doesn't work, outputs
"FAILED (remote: unknown command)"
Flashing recovery doesn't work either "partition 'recovery' not support flash" but that's probably because the bootloader is still locked. I've rooted this phone with Kingoroot but not having a TWRP recovery bothers me a lot, since this device would most likely get bricked if factory resetted because Gapps were deleted. Also Kitkat is outdated for 2018.
Is there any possibility to get the identifier token, so as to unlock this bootloader on 626g+ dual sim version?
Click to expand...
Click to collapse
there is a firmware for the phone
unpack it
u will find there file Checksum.ini
and unlock‐secro.img(or diferent name point is unlock)
rename checksum.ini on checksum.oem
then turn off all checks in flashtool leave marked only SECRO line
u must choose unlock‐secrom.img for SECRO line
once u'll flash SECRO u will have to flash twrp, to do that u must turn off all checks except RECOVERY, for RECOVERY u must open recovery 1.72.img then flash it, after u can just flash supersu.zip via twrp
i've done it all on my 1.76 device it will also work on 1.79
twrp u can find here(u need to register on that forum)
https://4pda.ru/forum/index.php?showtopic=756527&view=findpost&p=53228248

Related

stuck logo htc raider

Hi, about 6 months ago bought a rogers htc raider, upon receipt procedures to perform the unlock bootloader and s-off procedure, it will change back to a stock rom and I gave it to my brother, I recently comes for saying that when you turn the phone just stays on the logo screen, entering volume down menu and power, try to do a factory reset and get stuck, also download a stock rom and extracted the rom.zip file so renowned as ph39img.zip and try to run and do the updating also remains stalled, also try to lock the bootloader with fastboot oem lock and also stuck.
please i need help.
axel_johnson said:
Hi, about 6 months ago bought a rogers htc raider, upon receipt procedures to perform the unlock bootloader and s-off procedure, it will change back to a stock rom and I gave it to my brother, I recently comes for saying that when you turn the phone just stays on the logo screen, entering volume down menu and power, try to do a factory reset and get stuck, also download a stock rom and extracted the rom.zip file so renowned as ph39img.zip and try to run and do the updating also remains stalled, also try to lock the bootloader with fastboot oem lock and also stuck.
please i need help.
Click to expand...
Click to collapse
1. This should not be in the development section......
2. Boot to bootloader.
3. Does it say Locked, Relocked, or Unlocked?
4. Does it say S-On or S-Off?
5. Do you have v1.83 or 1.85 bootloader?
6. Select Recovery, what happens?
1. This should not be in the development section......
2. Boot to bootloader.
yes boot with volumen - and power
3. Does it say Locked, Relocked, or Unlocked?
Unlocked, i try locked again but nothing the phone still stuck, running the command fastboot oem lock.
4. Does it say S-On or S-Off?
s-off along a few months with the method juonot... with wire.
5. Do you have v1.83 or 1.85 bootloader?
show the version 1.85
6.- recovery
don't work when selected the option recovery the phone show the screen logo along 1 second and back to screen boot.
Next step would be fast boot flashing a custom recovery. I recommend wcx or twrp. Once youve done that, youll be set to properly wipe and flash the ROM of your choice
wcxjb hello and try but I can not, I get the following error.
C: \ Useful HTC One X \ WCXJB_ROOT_PACK \ WCXJB_ROOT_PACK> fastboot flash zip jb_hboot.
zip
******** sending 'zip' (379 KB) ... OKAY [0.318s]
***************** writing 'zip' ... FAILED (remote: not allowed)
finished. total time: 0.642s
please what else I can do ... I need to operate this phone.
Extract the wcxrecovery.IMG from the zip..
Fastboot flash recovery wcxrecovery.IMG
You can't fastboot flash a zip
I tried to do that and I get the following error.
C:\Utiles HTC One X\WCXJB_ROOT_PACK\WCXJB_ROOT_PACK>fastboot flash recovery wcxr
ecovery.img
sending 'recovery' (6996 KB)... OKAY [ 1.720s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 3.178s
please help me.
Is your Boot loader unlocked?
yes the bootloader is unlocked, i try locked o relocked but not possibly, the phone was stuck.
please help what steps should I follow ... I want to retrieve the phone.
axel_johnson said:
please help what steps should I follow ... I want to retrieve the phone.
Click to expand...
Click to collapse
The only things I can think of that would cause this "writing 'recovery'... FAILED (remote: image update error)" would be:
1. You got a bad download
2. Bootloader is not properly unlocked
3. Your recovery partition got borked somehow
Things I would try next:
1. Redownload the recovery image and try again
2. fastboot oem lock to lock the bootloader, then go through the unlock process again
3. fastboot oem lock, run your carrier's RUU, reunlock bootloader, fastboot flash recovery wcxrecovery.img, fastboot flash boot boot.img (from ROM), boot to recovery, wipe data, system, dalvik, and cache, and flash ROM
pleas help me my htc rider
My phone refuse to boot up to normal background it is stuck on the htc logo hv tried factry reset bt still no progress it was caused by an apps I installed phone name htc rider vrsn 4.0 pls help me

stuck in fastboot, cant flash anything, cant go to recovery

my phone: Nexus 6 32gb international
marshmallow (MRA58R) with cataclysm rom
twrp custom recovery and elementalx kernel
rooted, unlocked bootloader, no xposed
1. my phone was running fine until it randomly crashed and got stuck in fastboot menu. trying to start does nothing but in bootloader logs it shows this:
Code:
failed to validate boot image ret=-1
trying to reboot recovery gives:
Code:
failed to validate recovery image ret=-1
so i guess time to flash a MRA58R factory image right? however:
2. trying to flash via "flash all" script, manual one by one flash, or using the nexus root toolkit gives:
Code:
<bootloader> failed to flash partition
FAILED <remote failure>
this happens when i try to flash recovery (Stock or twrp) or bootloader or bootimage or system or anything. i have to my knowledge adequate platform tools setup which ive used multiple times before. my sdk tools are updated as well. at this point ill try anything. and i use windows. please help
Osaab said:
my phone: Nexus 6 32gb international
marshmallow (MRA58R) with cataclysm rom
twrp custom recovery and elementalx kernel
rooted, unlocked bootloader, no xposed
1. my phone was running fine until it randomly crashed and got stuck in fastboot menu. trying to start does nothing but in bootloader logs it shows this:
Code:
failed to validate boot image ret=-1
trying to reboot recovery gives:
Code:
failed to validate recovery image ret=-1
so i guess time to flash a MRA58R factory image right? however:
2. trying to flash via "flash all" script, manual one by one flash, or using the nexus root toolkit gives:
Code:
<bootloader> failed to flash partition
FAILED <remote failure>
this happens when i try to flash recovery (Stock or twrp) or bootloader or bootimage or system or anything. i have to my knowledge adequate platform tools setup which ive used multiple times before. my sdk tools are updated as well. at this point ill try anything. and i use windows. please help
Click to expand...
Click to collapse
Is the phone unlocked?
Code:
fastboot oem unlock
Can you erase userdata and cache
Code:
fastboot -w
mywindow said:
Is the phone unlocked?
Code:
fastboot oem unlock
Can you erase userdata and cache
Code:
fastboot -w
Click to expand...
Click to collapse
the phone is unlocked. it shows unlocked status 3 or something. and no -w gives the same error (failed to flash partition).
i was wondering i dont remember if i had "allow oem unlocking" enabled in the dev options and now i cant access it. is there a way that can be a problem?
Osaab said:
the phone is unlocked. it shows unlocked status 3 or something. and no -w gives the same error (failed to flash partition).
i was wondering i dont remember if i had "allow oem unlocking" enabled in the dev options and now i cant access it. is there a way that can be a problem?
Click to expand...
Click to collapse
I doubt it, since you don't need to unlock it a little more.
You should check your USB cable, or try to switch to another port. But if the error still persists, you need to send it to repair.
I am sorry mate, but u might have to send it in for real
Maybe your nand memory is corrupted. Since ur phone just crashed for "no reason" and then got stuck in fastboot, it may be an indicator for that.
Best regards!
Osaab said:
the phone is unlocked. it shows unlocked status 3 or something. and no -w gives the same error (failed to flash partition).
i was wondering i dont remember if i had "allow oem unlocking" enabled in the dev options and now i cant access it. is there a way that can be a problem?
Click to expand...
Click to collapse
I BELIEVE once you tick it and unlock, it does not turn back off (allow OEM unlock)
But as said above, this option only allows the bootloader to accept the unlock command...
Best case is the internal storage got scrambled and your partitions/ partition table is corrupt/missing/gone, worse case and maybe more likely is hardware failure?
Not sure if you can send terminal commands, but next step is either just RMA or searching the internet for a way to manually rebuild partition table from bootloader?
I guess?
Sounds like it messed it self up pretty good somehow, sorry man.

Oem bootloader locked with no os installed!!! How can i flash phone to stock?!

I have the Moto Nexus 6 (xt1100) with TRWP installed no backup saved, OEM bootloader locked and no OS currently on the phone and i cant reflash nethunter or any stock roms through TRWP or fastboot. PLZ HELP ME OUT.
You could to install by adb sideload some full ota.
There is a Android N preview that could be applied by adb sideload, once you have access to your phone, you could unlock bootloader and apply any other rom
lulzwolf said:
I have the Moto Nexus 6 (xt1100) with TRWP installed no backup saved, OEM bootloader locked and no OS currently on the phone and i cant reflash nethunter or any stock roms through TRWP or fastboot. PLZ HELP ME OUT.
Click to expand...
Click to collapse
Push a custom rom to your phone and flash it in TWRP. Command: adb push namerom.zip /sdcard/, or sideload a custom rom in also in TWRP recovery. And don`t ever relock your bootloader again if you are flasher If you have enabled ENABLE OEM UNLOCK in developer options its best to unlock it first
gee2012 said:
Push a custom rom to your phone and flash it in TWRP. Command: adb push namerom.zip /sdcard/, or sideload a custom rom in also in TWRP recovery. And don`t ever relock your bootloader again if you are flasher If you have enabled ENABLE OEM UNLOCK in developer options its best to unlock it first
Click to expand...
Click to collapse
He can't flash any ROM with a locked bootloader.
You should be able to fastboot flash a stock image, but if your fastboot isn't working then you're kinda screwed.
All I can say is give the fastboot flash another try, maybe from a different PC. Use method 2 in this guide to return to stock, then use the stock recovery to factory reset and boot it up
noidea24 said:
He can't flash any ROM with a locked bootloader.
You should be able to fastboot flash a stock image, but if your fastboot isn't working then you're kinda screwed.
All I can say is give the fastboot flash another try, maybe from a different PC. Use method 2 in this guide to return to stock, then use the stock recovery to factory reset and boot it up
Click to expand...
Click to collapse
I tried Macon's method but i am still unable to flash the phone back to stock. The OEM bootloader is locked and i cant access it without an OS installed. Is there a way i can bypass the OEM bootloader aka hack/root the phone to reflash it?
It should work if you run these commands (with the phone in bootloader) prior to flashing the custom rom zip in TWRP:
Fastboot format cache
Fastboot format userdata
Didgeridoohan said:
It should work if you run these commands (with the phone in bootloader) prior to flashing the custom rom zip in TWRP:
Fastboot format cache
Fastboot format userdata
Click to expand...
Click to collapse
"""
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'cache' (6248 KB)...
writing 'cache'...
(bootloader) Unlock before flashing
"""
"""
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
sending 'userdata' (139061 KB)...
writing 'userdata'...
(bootloader) Unlock before flashing
"""
Im still locked out of the bootloader. how do i circumvent the OEM bootlock? can i hack pass it? it is password protected somewhere, if it is can i bruteforce the password? how can i get pass it guyz?!?!
The OEM bootloader is locked and i cant gain access to the developer optios because i dont have an OS to boot into. Im looking for a way i can "bypass" "circumvent" "hack" "disable" or any other word you can think of to get around the bootloader lock and flash my phone. i can start an "adb shell" and gain access to the command line on the phone, but i dont know where i can find the "OEM Bootloader" part of the phone for modification. I have also tried running "fastboot oem get_unlock_data" but it says "(bootloader) This command is not needed to unlock. Run fastboot oem unlock" WTF.... DAMMIT FUK FUK FUK FUUUUUUUUUUUUUUUUUUUUUUUUUUJK
"""
The command i used below and its output message.
"""
[email protected]# fastboot oem unlock
"""
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.005s
"""
lulzwolf said:
"""
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'cache' (6248 KB)...
writing 'cache'...
(bootloader) Unlock before flashing
"""
"""
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
sending 'userdata' (139061 KB)...
writing 'userdata'...
(bootloader) Unlock before flashing
"""
Im still locked out of the bootloader. how do i circumvent the OEM bootlock? can i hack pass it? it is password protected somewhere, if it is can i bruteforce the password? how can i get pass it guyz?!?!
Click to expand...
Click to collapse
Sorry to hear that... The suggested method used to work for people unable to unlock their bootloader due to not having the setting checked in developers settings (if they had TWRP installed, of course).
I do believe you are screwed...
@lulzwolf: Contact Motorola and/or Google, because you screwed yourself by not leaving "Enable OEM Unlock" checked after you modified the firmware. There is no way to brute force the lock, unless you happen to be immortal. The encryption on the bootloader is sufficiently strong that you'll be dead long before a computer could successfully unlock it.
Lesson of the day folks: if you modify your Nexus 6, even if only to root it, leave "Enable OEM Unlock" checked! Yes, it will make your device less secure since a knowledgeable person can flash a factory image, but it's better than being permanently locked out of the device.
Just flash any rom trough TWRP. For god's sake, it even supports MTP. What's your problem?
@Lawstorant: Did you read the thread? His bootloader is locked, meaning he cannot flash anything.
@Strephon Alkhalikoi
It doesn't work that way. Locked bootloader only means that he cannot flash anything using fastboot, but he clearly said that he has TWRP. TWRP doesn't relay on fastboot (common knowledge 1) because it's a totally seperate thing, hence locked bootloader doesn't affect TWRP in any way. He can still do anything he likes. The simplest solution is to flash ANY rom trough TWRP and unlock bootloader with "Boot unlocker" app.
Locked bootloader means you cannot use fastboot, partitions are not unaccesible.
1. If you lock your Windows OS with password you can't acces it, but if you have Linux there's nothing that prevents you from browsing filse on windows partition (only encryption, but still, you can wipe it and put in, anything you want).
TL;DR You're wrong, go learn some more.
@Lawstorant, your attitude and tone need a bit of adjustment. If I am wrong, that's one thing. There is however no need to be a smart ass about it, especially with the TL;DR bit. It's juvenile, and uncalled for. That said, you are correct in that lulzwolf may not be totally screwed. Virtually everyone, including myself, has assumed he has to flash a stock image, but he really doesn't. We'll need him to answer one way or another, but the instructions to restore his device are as follows.
Boot into bootloader.
Use fastboot and issue the following commands: fastboot format userdata, fastboot format cache.
Reboot into TWRP.
Flash a custom ROM.
Unlock the bootloader, and leave it unlocked.
lulzwolf did in fact get at least as far as the two fastboot commands, but he does not say whether he got back into TWRP. Now that he has gotten the userdata and cache formatted he should be able to boot into TWRP and install a custom ROM. From there he should be able to unlock the bootloader.
So @lulzwolf, where are you getting stuck? You may not be done yet, as I erroneously assumed.
@Lawstorant: Did you read the thread? His bootloader is locked, meaning he cannot flash anything.
Click to expand...
Click to collapse
no need to be a smart ass about it,
Click to expand...
Click to collapse
formating trough fastboot won't succed, because he needs access to these partitions. Why would anyone even recommend fastboot when bootloader is locked? He's better of formatting them trough TWRP.
TWRP is answer to all questions. I don't even know why he's tinkering with his phone if he can't figure it out on his own.
Ask The_Merovingian. He wrote the guide. I simply copied it from his thread.
However, you and I do agree on one very important thing. If he doesn't know what he's doing he shouldn't be messing about with his phone, period. He did say in his opening post that he couldn't flash ROMs through TWRP, but given what's been posted, there shouldn't be any reason he can't flash a ROM, except he has a bigger issue than not having the OS.
Ok so i have solved my problem by installing a custom ROM called "Cataclysm" through the TRWP recovery tool. My problem was I tried flashing to stock with fastboot when fastboot had no access to the partitions. so i used adb to push a custom ROM and installed it in TRWP.... BOOM it was fixed! so in conclusion we have learned that fastboot cannot access partitions while the OEM bootloader is locked but TRWP can. thank you all for commenting and helping me out, and hopefully this thread can help out others who run across this problem in the future.
lulzwolf said:
I have the Moto Nexus 6 (xt1100) with TRWP installed no backup saved, OEM bootloader locked and no OS currently on the phone and i cant reflash nethunter or any stock roms through TRWP or fastboot. PLZ HELP ME OUT.
Click to expand...
Click to collapse
rofl, way to go
lulzwolf said:
Ok so i have solved my problem by installing a custom ROM called "Cataclysm" through the TRWP recovery tool. My problem was I tried flashing to stock with fastboot when fastboot had no access to the partitions. so i used adb to push a custom ROM and installed it in TRWP.... BOOM it was fixed! so in conclusion we have learned that fastboot cannot access partitions while the OEM bootloader is locked but TRWP can. thank you all for commenting and helping me out, and hopefully this thread can help out others who run across this problem in the future.
Click to expand...
Click to collapse
Which is exactly what gee2012 suggested that you should do in the second reply to your cry for help. (And at least I assumed you had tried without success. Serves me right for assuming...)
Glad it worked out. :good:
I hope you learned more than just that from this exercise. I know I did, namely a reminder to "practice what I preach". I tell people like you to search before posting and I failed to do just that. Mea culpa.

Cant Relock Bootloader

I can't relock my bootloader. Haven't rooted or anything. I unlocked it, couldnt flash the kernel for root so gave up on it and wanted to relock my bootloader. Getting these errors:
c:\adb>fastboot flashing lock_critical
FAILED (Write to device failed (No such file or directory))
fastboot: error: Command failed
Any ideas?
wschamps42 said:
I can't relock my bootloader. Haven't rooted or anything. I unlocked it, couldnt flash the kernel for root so gave up on it and wanted to relock my bootloader. Getting these errors:
c:\adb>fastboot flashing lock_critical
FAILED (Write to device failed (No such file or directory))
fastboot: error: Command failed
Any ideas?
Click to expand...
Click to collapse
Are you sure the kernel didn't flash at all?
I'd recommend flashing a factory image and then trying to lock it just in case something went wrong.
If it still doesn't work is your device showing on CMD using "fastboot devices"?
I'm getting the error device already locked even though my bootloader clearly states that the bootloader is in unlocked. I just flashed the factory image for the phone and still same error. Any ideas?
Rox598 said:
Are you sure the kernel didn't flash at all?
I'd recommend flashing a factory image and then trying to lock it just in case something went wrong.
If it still doesn't work is your device showing on CMD using "fastboot devices"?
Click to expand...
Click to collapse
hello i was able to get it to show up in fastboot devices but i am unable to relock...when i try to get it to relock it goes and says waiting for device even though its in fast boot mode.

Huawei p9 recovery fail!

I have a Huawei P9 and I rooted this previously and installed TWRP. Everything was fine and and just recently I flashed stock recovery so I can update my phone and relocked bootloader. When I locked it, it tried to restore to factory settings as it usually does and I get a prompt “wipe cache partition” or wipe something. I now can’t remember as I just absently tapped “yes.” And after that the phone was bricked. It tries to restore using eRecovery but always fails. I can’t flash through fastboot as the phone can’t be detected. Please help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
khangkhong said:
I have a Huawei P9 and I rooted this previously and installed TWRP. Everything was fine and and just recently I flashed stock recovery so I can update my phone and relocked bootloader. When I locked it, it tried to restore to factory settings as it usually does and I get a prompt “wipe cache partition” or wipe something. I now can’t remember as I just absently tapped “yes.” And after that the phone was bricked. It tries to restore using eRecovery but always fails. I can’t flash through fastboot as the phone can’t be detected.
Click to expand...
Click to collapse
What was your last action before you went to (re)lock Bootloader:
a) Flashing stock Recovery, and in that case did you unroot and are you sure it was correct Recovery version for the stock firmware you were running
or
b) Updating Firmware, and in that case by which method did you update (OTA, eReovery, HiSuite, DLOAD, Firmware Finder + DNS, HWOTA...)?
What is your model L09 or L19, your cust c432 or else, what was your full build name/number (like EVA-L09c432b504 or what)?
zgfg said:
What was your last action before you went to (re)lock Bootloader:
a) Flashing stock Recovery, and in that case did you unroot and are you sure it was correct Recovery version for the stock firmware you were running
or
b) Updating Firmware, and in that case by which method did you update (OTA, eReovery, HiSuite, DLOAD, Firmware Finder + DNS, HWOTA...)?
What is your model L09 or L19, your cust c432 or else, what was your full build name/number (like EVA-L09c432b504 or what)?
Click to expand...
Click to collapse
I tried updating my phone using the dload method but it kept failing. I also used a lot of firmwares. Btw my phone is EVA-L19 and I live in the Philippines and got my phone here. I only used the Asia firmwares as I can't seem to find a Philippine specific firmware. I did not unroot before relocking the bootloader.
khangkhong said:
I tried updating my phone using the dload method but it kept failing. I also used a lot of firmwares. Btw my phone is EVA-L19 and I live in the Philippines and got my phone here. I only used the Asia firmwares as I can't seem to find a Philippine specific firmware. I did not unroot before relocking the bootloader.
Click to expand...
Click to collapse
Before relocking Bootloader you must make sure that you have stock Recovery, stock Boot/Ramdisk image (that is, must be unrooted), stock Kernel (if you experimented with custom Kernels).
Unfortunately, if you didn't have, Factory reset as part of relocking Bootloader fails and may cause brick
Don't know what is the cust for Philippines/Asia and what are its latest firmware versions, and do they allow DLOAD installations (only firmwares named as FullOTA-MFPV on Firmware Finder can be installed by DLOAD, those with MF but without PV cannot be).
Btw, what is the cust for Asia you were flashing with, EVA-L19cXXX?
If eRecovery cannot recognize the phone model, it might be due your attempts to flash various firmwares by DLOAD
Can you boot to Fastboot and connect by Fastboot from PC (probably no more since you attempted to relock Bootloader, which disabled OEM Unlock and USB debugging):
- Switch off, connect by USB to PC, press and keep pressing Vol- and press Pow button.
If you could boot to Fastboot, there are Fastboot commands to read what the phone thinks it is its latest cust and build number, that can help to unbrick.
Also, it helps to DC-Phoenix (paid tool for unbricking)
PS: Don't know why people go for relocking Bootloader. There have been so many posts here and there with users who bricked their phones when attempting to re-lock Bootloader(because they had TWRP, they did not unroot, they had custom DOMs, etc).
Besides:
- Unlocked Bootloader DOES NOT prevent/affect OTA upgrades
- relocked Bootloader is different from originally locked Bootloader and Huawei service can still recognize that Bootloader was unlocked and relocked
- Some new stock firmwares automatically lock (not relock) Bootloaders upon upgrades
I can boot to fastboot but all of the tutorials I’ve read says that the bootloader needs to be unlocked in order to upgrade firmware or unbrick. And the only commend I can do in fastboot is “fastboot devices.”
khangkhong said:
I can boot to fastboot but all of the tutorials I’ve read says that the bootloader needs to be unlocked in order to upgrade firmware or unbrick. And the only commend I can do in fastboot is “fastboot devices.”
Click to expand...
Click to collapse
What does it respond you on commands
Code:
fastboot oem get-bootinfo
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem get-build-number
fastboot oem oeminforead-SYSTEM_VERSION
zgfg said:
What does it respond you on commands
Code:
fastboot oem get-bootinfo
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem get-build-number
fastboot oem oeminforead-SYSTEM_VERSION
Click to expand...
Click to collapse
fastboot oem get-bootinfo = (bootloader) unlocked
fastboot oem get-product-model = (bootloader) EVA-L19
fastboot getvar vendorcountry = vendorcountry: hw/spcseas
fastboot oem get-build-number = (bootloader) :EVA-L19C636B398
fastboot oem oeminforead-SYSTEM_VERSION = (bootloader) :EVA-L19C636B398
khangkhong said:
fastboot oem get-bootinfo = (bootloader) unlocked
fastboot oem get-product-model = (bootloader) EVA-L19
fastboot getvar vendorcountry = vendorcountry: hw/spcseas
fastboot oem get-build-number = (bootloader) :EVA-L19C636B398
fastboot oem oeminforead-SYSTEM_VERSION = (bootloader) :EVA-L19C636B398
Click to expand...
Click to collapse
As per your Fastboot - your Bootloader is still Unlocked
Hence flash TWRP for Nougat (from Fastboot) and use HWOTA method:
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
to flash EVA-L19C636B398.
It must be FullOTA-MF, it is explained in the link above what you need to prepare (HWOTA folder on the SD card, that contains three PROPERLY renamed update*.zip files that you must find and download by Firmware Finder, you can use FF on PC).
It can be any other NOUGAT stock firmware (not necessarily b398) but it must be for EVA-L19c636 (by HWOTA alone you cannot rebrand to eg c432) and it must be FullOTA-MF (or MFPV), usually 2+ GB, not some OTA-MF of only 300 MB or so.
You must use the same TWRP for Nougat that you will find in the post #1, from the same thread as above, where is HWOTA method describef in the post #3.
If you use Windows 10 on the PC, (by default it hides file extensions) make sure that you do not rename some of the three update*.zip files to have 'double' zip extensions like update*.zip.zip
In HWOTA method, TWRP will execute a shell script and files and folders must be named exactly as described in the given OP post, otherwise HWOTA method (its shell script) will fail to flash the complete firmware
@zgfg sorry for disturb
can u help me i dont want make new thread
here is my problem
i unlock boorloader and install TWRP and use stock fraimware i use for while but i want to factory rest my phone after that my phone cant boot up
still i can access to TWRP
what can i do ?
can i use system recovery on hi suite?
misagh72 said:
@zgfg sorry for disturb
can u help me i dont want make new thread
here is my problem
i unlock boorloader and install TWRP and use stock fraimware i use for while but i want to factory rest my phone after that my phone cant boot up
still i can access to TWRP
what can i do ?
can i use system recovery on hi suite?
Click to expand...
Click to collapse
People, this has been written in many other threads and posts:
- Before doing Bootloader relock or Factory reset, you must unroot, restore stock Recovery, otherwise it bricks.
You can try to reinstall by using eRecovery.
But since you still have TWRP, read my post #8, you have link and instructions to the HWOTA method.
Of course, I have described to the other user who has L19c636, you must flash by HWOTA for your model L09/L19 and your cust cXXX - I gave instructions in the posts #4 and #6 how to boot to Fastboot and which Fastboot commands to use to obtain info for your phone
zgfg said:
As per your Fastboot - your Bootloader is still Unlocked
Hence flash TWRP for Nougat (from Fastboot) and use HWOTA method:
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
to flash EVA-L19C636B398.
It must be FullOTA-MF, it is explained in the link above what you need to prepare (HWOTA folder on the SD card, that contains three PROPERLY renamed update*.zip files that you must find and download by Firmware Finder, you can use FF on PC).
It can be any other NOUGAT stock firmware (not necessarily b398) but it must be for EVA-L19c636 (by HWOTA alone you cannot rebrand to eg c432) and it must be FullOTA-MF (or MFPV), usually 2+ GB, not some OTA-MF of only 300 MB or so.
You must use the same TWRP for Nougat that you will find in the post #1, from the same thread as above, where is HWOTA method describef in the post #3.
If you use Windows 10 on the PC, (by default it hides file extensions) make sure that you do not rename some of the three update*.zip files to have 'double' zip extensions like update*.zip.zip
In HWOTA method, TWRP will execute a shell script and files and folders must be named exactly as described in the given OP post, otherwise HWOTA method (its shell script) will fail to flash the complete firmware
Click to expand...
Click to collapse
I followed all the steps and downloaded all files and put them into HWOTA and rebooted. Nothing happens. I tried Vol+, Vol-, and Power button to force to install files but I get install failed. BTW when I boot I'm always on eRecovery and cannot boot to TWRP.
khangkhong said:
I followed all the steps and downloaded all files and put them into HWOTA and rebooted. Nothing happens. I tried Vol+, Vol-, and Power button to force to install files but I get install failed. BTW when I boot I'm always on eRecovery and cannot boot to TWRP.
Click to expand...
Click to collapse
>> downloaded all files and put them into HWOTA and rebooted. Nothing happens
Nothing can happen by itself
>> . I tried Vol+, Vol-, and Power button to force to install files
This is HWOTA, not DLOAD.
It's desrcribed in the HWOTA tutorial that you must boot to TWRP, and TWRP has Install tab where you choose Storage (SD card), Zip installation, and then select the script from HWOTA folder, and then Swipe to start flashing
>> when I boot I'm always on eRecovery and cannot boot to TWRP
I wrote you in the previous post that you must first install TWRP. Your Bootloader says it is unlocked.
You must install TWRP from the thread I gave you the HWOTA link - do you know how to install TWRP from Fastboot?
Have the HWOTA folder ready on the SD card, so that when you install TWRP from Fastboot, you must immediately reboot from Fastboot directly to TWRP, then navigate in TWRP to it's Install option and proceed by HWOTA installation as described in its OP post
I tried installing TWRP in fastboot mode using “fastboot flash recovery” command but it always fails. Btw I can only boot to eRecovery so the developer options and usb debugging that needs to be toggled cannot be done. Cause in all tutorials to flash TWRP, usb debugging needs to be toggled.
khangkhong said:
I tried installing TWRP in fastboot mode using “fastboot flash recovery” command but it always fails. Btw I can only boot to eRecovery so the developer options and usb debugging that needs to be toggled cannot be done. Cause in all tutorials to flash TWRP, usb debugging needs to be toggled.
Click to expand...
Click to collapse
Please describe how flashing TWRP fails - what exactly does the Fastboot respond to the command.
Please copy/paste your command and the Fastboot response from the PC
And please upload also a photo of the phone Fastboot screen, what exactly it says on the bottom (Phone unlocked...)
zgfg said:
Please describe how flashing TWRP fails - what exactly does the Fastboot respond to the command.
Please copy/paste your command and the Fastboot response from the PC
And please upload also a photo of the phone Fastboot screen, what exactly it says on the bottom (Phone unlocked...)
Click to expand...
Click to collapse
This is the prompt.
target reported max download size of 471859200 bytes
sending 'recovery' (25220 KB)...
OKAY [ 0.558s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.586s
On my phone in fastboot mode:
khangkhong said:
This is the prompt.
target reported max download size of 471859200 bytes
sending 'recovery' (25220 KB)...
OKAY [ 0.558s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.586s
On my phone in fastboot mode:
View attachment 4755207
Click to expand...
Click to collapse
From your Fastboot screen photo:
- Phone relocked (green)
Hence Bootloader is really relocked, but this is in contradiction to
>> Bootloader unlocked
what was reported by Fastboot interrogation from the PC side, post #7
Btw, you see that Fastboot screen says Phone (=Bootloader) relocked (it was unlocked and then locked) clearly distinguishing from the originally locked phone (Bootloader) ;-(
Fastboot also shows
- FRP locked (green)
which confirms that OEM is locked.
Btw, did you maybe locked OEM from Settings, Developer options before you went to relock Bootloader by Fastboot?
Unfortunately, you got what you wanted, the locked Bootloader and also locked OEM - but since the phone is bricked (you didn't prepare to have stock and unrooted firmware with stock Recovery before attempting to relock Bootloader), you cannot unbrick the phone now:
- Methods require to have or to flash TWRP (like HWOTA)
- Or to flash stock Recovery, etc:
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7
https://forum.xda-developers.com/p9/how-to/unbrick-huawei-p9-eva-l19-100-t3628656
https://forum.xda-developers.com/p9/how-to/huawei-p9-brick-easiest-to-unbrick-t3662348
- Or to flash no-check Recovery:
https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
But you locked Bootloader and they cannot flash anything.
Because OEM is also locked, you cannot unlock Bootloader.
And you cannot boot to System to unlock OEM (on the bricked phone).
Btw, it was much more useful working phone with unlocked Bootloader and OEM (bothering with a Notice on the start screen) but available for unbricking (just in case), than now the phone with locked Bootloader and OEM albeit bricked ;-(
I hope, somebody else a wannabe with the relocked Bootloader will read this (they don't, every month or so another one does the same or similar and only then turn to XDA asking for help)
---
Anyway, you can try:
1) Download by Firmware Finder (from another phone, needs not to be Huawei, you can install FF from GStore to any Android) or from PC, EVA-L19c636b395 FullOTA-MFPV (package number #114776, 2.5 GB) as on the screenshot.
Try to DLOAD.
No guarantee that it could work (your phone remembers b398 and there is no MFPV with c636 but b398 or higher)
2) Try to rollback to Marshmallow, maybe it will allow you to do it by DLOAD:
https://forum.xda-developers.com/p9/help/finally-downgrade-huawei-p9-android-t3868721
Once on Marshmallow (but with unbricked phone), update by OTA back to Nougat
Sorry, I don't know any other (free) method (all others require flashing, but you cannot since the Bootloader OEM are locked)
You can try paid services, people were able to unbrick (with locked Bootloader and OEM) by using their tools, but you must directly communicate over the Web links, pay them and ask for instructions:
3) DC Phoenix:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
4) Ministry of Solutions:
https://ministryofsolutions.com/paid-services/amp
zgfg said:
From your Fastboot screen photo:
- Phone relocked (green)
Hence Bootloader is really relocked, but this is in contradiction to
>> Bootloader unlocked
what was reported by Fastboot interrogation from the PC side, post #7
Btw, you see that Fastboot screen says Phone (=Bootloader) relocked (it was unlocked and then locked) clearly distinguishing from the originally locked phone (Bootloader) ;-(
Fastboot also shows
- FRP locked (green)
which confirms that OEM is locked.
Btw, did you maybe locked OEM from Settings, Developer options before you went to relock Bootloader by Fastboot?
Unfortunately, you got what you wanted, the locked Bootloader and also locked OEM - but since the phone is bricked (you didn't prepare to have stock and unrooted firmware with stock Recovery before attempting to relock Bootloader), you cannot unbrick the phone now:
- Methods require to have or to flash TWRP (like HWOTA)
- Or to flash stock Recovery, etc:
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7
https://forum.xda-developers.com/p9/how-to/unbrick-huawei-p9-eva-l19-100-t3628656
https://forum.xda-developers.com/p9/how-to/huawei-p9-brick-easiest-to-unbrick-t3662348
- Or to flash no-check Recovery:
https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
But you locked Bootloader and they cannot flash anything.
Because OEM is also locked, you cannot unlock Bootloader.
And you cannot boot to System to unlock OEM (on the bricked phone).
Btw, it was much more useful working phone with unlocked Bootloader and OEM (bothering with a Notice on the start screen) but available for unbricking (just in case), than now the phone with locked Bootloader and OEM albeit bricked ;-(
I hope, somebody else a wannabe with the relocked Bootloader will read this (they don't, every month or so another one does the same or similar and only then turn to XDA asking for help)
---
Anyway, you can try:
1) Download by Firmware Finder (from another phone, needs not to be Huawei, you can install FF from GStore to any Android) or from PC, EVA-L19c636b395 FullOTA-MFPV (package number #114776, 2.5 GB) as on the screenshot.
Try to DLOAD.
No guarantee that it could work (your phone remembers b398 and there is no MFPV with c636 but b398 or higher)
2) Try to rollback to Marshmallow, maybe it will allow you to do it by DLOAD:
https://forum.xda-developers.com/p9/help/finally-downgrade-huawei-p9-android-t3868721
Once on Marshmallow (but with unbricked phone), update by OTA back to Nougat
Sorry, I don't know any other (free) method (all others require flashing, but you cannot since the Bootloader OEM are locked)
You can try paid services, people were able to unbrick (with locked Bootloader and OEM) by using their tools, but you must directly communicate to them, pay them and ask for instructions:
3) DC Phoenix:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
4) Ministry of Solutions:
https://ministryofsolutions.com/paid-services/amp
Click to expand...
Click to collapse
Thanks for the reply. I’ll try your suggestions.

Categories

Resources