Hello guys,
i have a problem. I installed the new rom on my x626 and it worked great, after that i locked bootloader by my mistake and the phone died (bricked with red light)
i followed the instruction with the unbrick, but i am unable to install anything new because the bootloader is locked.
The phone also is in the bootloap state without any recovery. I got acces to fastboot mode only.
I followed a guide, it worked once on my another le s3 x626 but right now it dont want to work because bootloader is locked.
when i put "fastboot oem unlock" - it says that operation is not allowed. I am stuck at this point.
I know that i made mistake, i am idiot but I will be very pleased if someone experienced could help me.
gozef14 said:
Hello guys,
i have a problem. I installed the new rom on my x626 and it worked great, after that i locked bootloader by my mistake and the phone died (bricked with red light)
i followed the instruction with the unbrick, but i am unable to install anything new because the bootloader is locked.
The phone also is in the bootloap state without any recovery. I got acces to fastboot mode only.
I followed a guide, it worked once on my another le s3 x626 but right now it dont want to work because bootloader is locked.
when i put "fastboot oem unlock" - it says that operation is not allowed. I am stuck at this point.
I know that i made mistake, i am idiot but I will be very pleased if someone experienced could help me.
Click to expand...
Click to collapse
Here is the solution to your problem !!!
https://forum.xda-developers.com/le-2/help/brick-restoration-flashtool-s28-x620-t3754590
I have the same problem, here's an output of some commands:
fastboot oem unlock:
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 9.629s
fastboot flashing get_unlock_ability:
(bootloader) unlock_ability = 0
OKAY [ 0.006s]
finished. total time: 0.007s
fastboot getvar unlocked:
unlocked: no
finished. total time: 0.002s
marksklava said:
I have the same problem, here's an output of some commands:
fastboot oem unlock:
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 9.629s
fastboot flashing get_unlock_ability:
(bootloader) unlock_ability = 0
OKAY [ 0.006s]
finished. total time: 0.007s
fastboot getvar unlocked:
unlocked: no
finished. total time: 0.002s
Click to expand...
Click to collapse
You have to turn on Oem unlock within Developer settings. Use the " all in one to tool"to unlock to he bootloader or flash emmc.boot while the phone is in fast boot mode.
KittyQueen said:
You have to turn on Oem unlock within Developer settings. Use the " all in one to tool"to unlock to he bootloader or flash emmc.boot while the phone is in fast boot mode.
Click to expand...
Click to collapse
I do not have access to android, my phone is bricked, i cannot unlock the bootloader that way.
Related
I'm getting the below Error.
D:\Sunil\Flashing cmd\fastboot_with_Android_USB_file\fastboot>fastboot.exe -i 0x
0fce getvar version
version: 0.3
finished. total time: 0.001s
D:\Sunil\Flashing cmd\fastboot_with_Android_USB_file\fastboot>fastboot.exe -i 0x
0fce oem unlock 0xDF461896BE2C2246
...
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.003s
D:\Sunil\Flashing cmd\fastboot_with_Android_USB_file\fastboot>
From the Sony website, did you follow these steps:
First, you should confirm that it is possible to unlock the boot loader of your phone by checking the service menu. In your phone, open the dialler and enter *#*#7378423#*#* to access the service menu.
In your phone, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
Hi everyone, I'm done and out of any ideas. Never before have I bricked my phone . Now I don't know what to do. Played before only with Samsung phones, they were waaay easier to play with.
Let me tell you my story:
1. Got P9 Lite with L21C22B120 rom (brand C22 from Poland)
2. No newer version available, decided to debrand / apply newer - flashed L21C432B161 (~3GB update.app), info showed L21C900B161 - need to change oeminfo etc.
3. [SRK Tool ] Unlocked bootloader and installed TWRP
4. [SRK Tool + TWRP] Built Root method via adb sideload failed, so installed SuperSu via TWRP from another source - success
5. [SRK Tool] Flashed oeminfo C432 Europe - success, but after that info showed C432B161 without L21
6. Flashed once more with the same B161 firmware - perfect info L21C432B161 but UI theme and icons got corrupted like that: https://forum.xda-developers.com/p9-plus/help/wrong-icons-c900-to-c432-failed-im-t3490561 and tried to flash mentioned hw_folder with SRK Tool.
7. [TWRP] Played with wipe / factory reset - couldn't boot anymore, TWRP showed "No OS installed" and "unable to mount /data" (it had 0MB, couldn't wipe it)
8. Then RESCUE MODE showed up and still I can't pass by it - exactly like here: https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-screen-please-help-t3244872 - only fastboot&rescue available.
What I have tried several times:
1. Flashing firmware C432B161 and C432B120 - failure at 5% (incompatibility)
2. Fastboot flash boot.img, recovery.img, system.img and cust.img (extracted from B120 and B161)- success, still rescue mode loop
3. Locking and unlocking bootloader with SRK Tool, flashing stock recovery and TWRP - success, still unable to load any recovery
4. Fastboot flashing FW_hifi.img - FAILED <remote: command not allowed>
Summary:
1. Looped Rescue mode shows: Please update system again, Func no : 8 (hifi image), Error no : 1 (security verify failed)
2. Fastboot&Rescue mode shows: Phone unlocked, FRP Unlock. Fastboot works.
3. Flashing main images doesn't change enything, can't flash corrupted(?) hifi image.
4. Maybe there is something wrong with my Bootloader? Is it truly unlocked? SRK Tool shows bootloader "unlocked" but many of the fastboot commands (i.e. getvar or oem) return "Failed, remote: command not allowed"
Any ideas in any of your clever or experienced heads? Should I try to flash that magical hifi image somehow or to flash some "compatibile" firmware (don't know which one wouldn't return that error).
Tried some fastboot commands, seems like I have found the reason for ROMs incompatibility:
fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.071s
fastboot getvar rescue_phoneinfo
rescue_phoneinfo: VNS-C432B161
finished. total time: 0.011s
fastboot oem get-product-model
...
(bootloader) hi6250
OKAY [ 0.011s]
finished. total time: 0.013s
fastboot oem get-psid
...
(bootloader) SN:BUC4C16929(...)
(bootloader) IMEI:863126032(...)
(bootloader) IMEI:863126032(...)
OKAY [ 0.011s]
finished. total time: 0.012s
fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
fastboot oem check-rootinfo
...
(bootloader) old_stat: SAFE
(bootloader) now_stat: SAFE
(bootloader) change_time: 0000000000
(bootloader) Check System: Decode fail
OKAY [ 0.018s]
finished. total time: 0.020s
fastboot oem get-build-number
...
(bootloader) :VNS-C432B161
OKAY [ 0.012s]
finished. total time: 0.013s
fastboot oem device-info
...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
What happened to L21 model in my build and model number? Is it corrupted?
Install os manually via adb mounting boot system and the other two things (i don't remember all and i don't have any link)
You can go to Twrpmeticulus?
Thanks guys! I flashed Meticulus TWRP - still couldn't enter it but accidentally discovered the (weird) way. I could go to it only with USB cable connected to computer and by pressing Vol+, Vol- and Power simultaneously, releasing them upon Huawei Logo. From there (TWRP) I rooted my device (adb sideload SuperSU 2.65), replaced oeminfo file via this tutorial - https://forum.xda-developers.com/huawei-p9lite/how-to/request-oeminfo-c432-p9-lite-t3427386 - and voila, I could finally flash C432B161 ROM without incompatibility error. Problem solved, hifi error gone of course.
I need to send my htc bolt in for warranty repair. How do I return to full original stock state?
I can run the RUU.exe to return to stock os, but I still remain s-off, unlocked. Can anyone help me get back to s-on and locked?
Thanks.
marcram said:
I need to send my htc bolt in for warranty repair. How do I return to full original stock state?
I can run the RUU.exe to return to stock os, but I still remain s-off, unlocked. Can anyone help me get back to s-on and locked?
Thanks.
Click to expand...
Click to collapse
I don't think it's possible to get it back to locked...
fastboot oem lock will get it "relocked"
fastboot oem writesecureflag 3 should get it back to s-on
Thanks for the response
Oem lock didn't work on the bolt, but I haven't tried the other command. I'm hoping I can at least get s-on. Maybe sunshine will give options to the bolt after s-on...
Didn't realize I didn't need s off for flashing roms.
I'm not having luck with the suggested commands:
D:\HTCBolt\fastboot-win>
D:\HTCBolt\fastboot-win>fastboot devices
HT6B404***** fastboot
D:\HTCBolt\fastboot-win>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.016s
D:\HTCBolt\fastboot-win>fastboot oem writesecureflag 3
...
FAILED (remote: unknown command)
finished. total time: 0.014s
D:\HTCBolt\fastboot-win>
D:\HTCBolt\fastboot-win>fastboot oem ?
...
FAILED (remote: unknown command)
finished. total time: 0.007s
D:\HTCBolt\fastboot-win>
Nevermind, guess I wasn't in download mode on the phone:
D:\>fastboot oem writesecureflag 3
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_PASS (0)
(bootloader) Partition verify pass
(bootloader) Write security level S-ON
OKAY [ 0.897s]
finished. total time: 0.900s
D:\>
Now to see how to lock.
NA
Here is how to get it back to Locked
https://forum.xda-developers.com/bolt/how-to/guide-set-bootloader-to-locked-unlocked-t3542131
Hello, got a CrossCall Core M4, and after some searchs, I could not find any public witness about successfull root for any device from this brand.
# fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
Click to expand...
Click to collapse
And nobody ever solved this.
try `fastboot flashing unlock` and make sure oem unlocking is turned on in the developpers settings
I have tried to unlock my bootloader using fastboot flashing unlock and fastboot flashing unlock_critical, however I get the error message:
Code:
(bootloader) Start unlock flow
FAILED (remote: '
Unlock operation is not allowed
')
fastboot: error: Command failed
I have turned on OEM unlocking in developer settings, and the output of fastboot flashing get_unlock_ability is:
Code:
(bootloader) unlock_ability = 16777216
OKAY [ 0.002s]
Finished. Total time: 0.002s
From that output, the bootloader unlock should work, however, it does not. Please help me.