can't unlock bootloader critical and other things.. - Nokia 8 Questions & Answers

ok guys so my dad has bricked his nokia .8.. i managed to get Twrp working again. and that's about it.. the bootloader is unlocked but i cant can't unlock "bootloader critical" it says something like " (remote command not allowed)" when i check the device info it says bootloader is unlocked but bootloader critical is not.. iv tried flashing via the ost but it says i need to unlock the critical bootloader..
another problem is that i cant flash in twrp. it says invalid zip file or something...
has anyone got a Twrp Backup they could upload so i can try and get this thing working again? or a zip i can flash via twrp?
cheers.

Did you do "fastboot flash unlock <path to unlock.key>" before trying to execute "fastboot oem unlock_critical"?
Did you maybe have an unlock key that was generated through the unofficial unlock (every build before august 2018) and are now on a newer build that supports only the official unlock?
If you can't manage to unlock the bootloader to critical, get some stock boot image (I have some at https://bit.ly/nokia-nb1), flash that to your active boot partition in fastboot (overwrite TWRP with it), then boot into stock recovery and sideload a full OTA package (which will restore all partitions that might be corrupted). All 1.5 GB files you can see in the OTA folder at the link I posted are full OTAs and will work.

ok so just an update i managed to get a rom on there, i found the right key and did the unlock all over again.. all booted ok, problem now is that i have no signal... i cant send any mssgs or phone calls. i tired to update the smsc. via this *#*#4636#*#*. and going phone info etc, but it says update error, iv also tried the encoded number for ee, but still says update error. i can put the sim card into another phone and it will send messages etc, i did read that i could update the smsc on a diffrent phone then put it back into the nokia and it will work, but it did not for me...
again there was another video showing how to fix this via backing up the firmware folder on rom then replacing with the one that dose not work . but ... i dont have a rom that works lol . iv also tried to install diffrent roms or systems and still the same problem.. i use the NOST tool. to update the firmware
any advice????
also this is his account hence a diffrent account name lol
cheers

Related

[Q] need some serious help with return to stock

hi all,
sorry to sound like a complete idiot in advance !
I have been trying for over a month now to find some way to return my phone to stock so I can get the new ota update but im just having no luck !
I have tried everything to unroot , relock boot loader, and return to stock, I can successfully unroot, successfully relock the boot loader but cannot update OTA everytime I download the ota and allow the phone to start update process the phone boots into bootlaoder and a new line appears in the normal messages **** security warning*** when this happens I loose recovery and the phone hasn't updated. I then have to re-unlock the bootloader to then flash a recovery.
I cant flash RUU as there isn't an RUU available for me, H3G_001 , I have tried the suggested CWM nandroid backup, but this fails half way through something to do with android_secure
I cant seem to get the phone to successfully grant s-off to try the change cid method, I have tried to do this using HTC one kit by hasoon but no luck,
if anyone could please help it would me much appreciated
regards
okz19
Probably you don't have the stock rom or the recovery, because the secure warning come out when you aren't fully stock..
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Justin2003 said:
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Click to expand...
Click to collapse
Is better link to XDA
still stuck!
hi all as you can probably tell form the age of this topic, I have been stuck for a while !!! (11 October ! )
I am still having problems trying to get the new update 2.24.771.3
my phone is carrier locked to three uk
it is unrooted
custom recovery cwm touch
bootloader unlocked / tampered
I understand I need stock recovery and to lock bootloader
I don't have stock rom
my problem is as follows, my phone has been telling me for atleast 4 months now that I have a software update, when I click it it restarts takes me to cwm recovery verifys install then gets stuck on cannot mount data ....
I understand I need to flash stock recovery, I have tried to do this using the "all in one kit" however when I click flash my own recovery, (phone reboots into bootloader) I then proceed to select the stock recovery.img the cmd box then hangs "waiting for device" I am then alerted by my computer that the usb device has malfunctioned. ( I am on windows 8 and have turned of signature verification)
I cannot use the supposed simple method of RUU as there isn't one available for my stupid network!!
I have tried to use a cwm recovery image, this usually starts then spits out android_secure is missing.
yes I do have a hammer ready to hit the phone with, but just before I do this is there ANYONE with any last tips to help me, because ive just about had enough with this stupid phone !
the phone has 24 hours left to live, can you save its life ?
thanks in advance for any help.
1. You cannot install an OTA with a custom recovery.
2. I've encountered a CWM bug having to do with .android_secure. There's a hidden folder in /sdcard that caused it, I don't remember whether this file is ".android_secure" or another. You can probably wipe the sdcard before restoring the backup. If that fails, you can probably manually restore the backup with ADB (this will be hard).
3. If you want to install the custom recovery, boot to the fastboot and use USB to install the recovery. Don't use a toolkit because they're useless when anything goes wrong.

Need help REMOTE COMMAND NOT ALLOWED (Can't go back to stock)

I have an L19C900B220 origanally C185, I tried changing the cust and got stuck on C900, and I also lost root access for some reason, so I tried to reboot to TWRP but it would just take me back to huawei recovery, so I went on SRK and tried to reflash TWRP and it gave me an error (Remote command not allowed) I tried to relock the bootloader same error, I tried to flash the revcovery.img through adb and got the same error, and I checked that OEM unlock was turned on, any ideas? Also DLOAD method gives me something along the lines of your deivce isn't compatible with this software or something
EDIT: NOW ON TWRP 3.1.0-0 can't mount data or system, can't do a data format either, don't know where to go from here, also lost access to use my phone so need an urgent fix, found out I'm still on NRD90M test-keys firmware
EDIT: Flashed recovery and boot, tried to flash system.img it said it worked in SRK, but my phone would be stuck on the bootloader warning screen
From where did you download your firmware? Use official website to download for right and not corrupted firmware.
kyle_2103 said:
I have an L19C900B220 origanally C185, I tried changing the cust and got stuck on C900, and I also lost root access for some reason, so I tried to reboot to TWRP but it would just take me back to huawei recovery, so I went on SRK and tried to reflash TWRP and it gave me an error (Remote command not allowed) I tried to relock the bootloader same error, I tried to flash the revcovery.img through adb and got the same error, and I checked that OEM unlock was turned on, any ideas? Also DLOAD method gives me something along the lines of your deivce isn't compatible with this software or something
Click to expand...
Click to collapse
I had the same issue, I had to use DC Phoenix to restore mine, which was a total pain

ran unlock_N4 Verizon Bootloader Unlocker on my t Mobile Note 4

now my phone lags freezes crashes reboots and does random weird s*** all the time I figured out that the files that came out on the SD card when I ran the script are from /firmware-modem/image. My phone is a mess HELLLLL LP
A folder named image came out on the SD card when I ran the unlock_N4 file. When I reflash stock Odin firmware it gave me an error message device does not have drk please indlstall drk and press any button and DMVerity verification failed when it went into recovery afterwards. The serial number is off also. Anybody know how to use fastboot with ADB to flash all the files back in????
did you try Kies?
lincolnsxda said:
now my phone lags freezes crashes reboots and does random weird s*** all the time I figured out that the files that came out on the SD card when I ran the script are from /firmware-modem/image. My phone is a mess HELLLLL LP
A folder named image came out on the SD card when I ran the unlock_N4 file. When I reflash stock Odin firmware it gave me an error message device does not have drk please indlstall drk and press any button and DMVerity verification failed when it went into recovery afterwards. The serial number is off also. Anybody know how to use fastboot with ADB to flash all the files back in????
1st why you ran Verizon bootloader to this phone? this phone has unlocked bootloader it doesnt need to be unlocked
2nd your phone partition got messed up you have to put TWRP back and then go in wipe and then you have to do file repair
3rd when you fix file then ran back the stock firmware which will fix bootloader
then go back install twrp and install custom rom with root, remember 910t, 910t3 comes with unlocked bootloaders no need to unlock them
Click to expand...
Click to collapse

twrp on p9 problem

Hello everyone, I wanted to revert to stock from bluewei, i flashed stock rom via dload method, but now it just bootloops. so i wanted to install twrp again so i can flash stock through twrp or atleast flash bluewei again but every time i try to flash with fastboot flash recovery command it says "remote: command not allowed", even tho i have my bootloader unlocked (everytime i turn on my phone it shows the warning that it is unlocked).
now i cant install twrp, cant flash through hisuite (it says that my device is not supported, tried the trick with changing ip address and port, nothing) and i dont have a idea how to make my phone useful again
Please can someone help me? THANKS!
p.s. device is p9 L09

Failed to install global rom via mi flashing tool, now phone stuck on fast boot.

Solved !!!
I was able to flash global miui 9.5.
Hi ,
So after finally the bootloader is unlocked I tried to flash the global rom via mi flash tool.
Update failed and an error message is update crc list failed !
I tried flashing back the chinse rom and I get the same error.
I can boot the device to recovery mode, but its mi recovery 3.0, I have 3 options:
1.wipe data
2. boot to system
3. connect via pc suite
tried with pc suite but it says my device isn't supported.
The computer recognizes the device via MiFlash tool but in adb via cmd when I type adb devices I get blank row and its unable to find the device.
how can I make my phone usable again please?
I have tried many things I found on google but nothing worked.
Thank you all
Hi
Is fastboot mode able?
Try to unlock again.
what do you mean able?
the phone is recognized via Mi Flash tool but in adb via cmd it is not recognized.
I waited 700 hours for the unlock and the phone is unlocked.
can you explain please what is fastboot able and what do you mean to try to unlock again?
thx
Hi
Could you start the phone in fastboot mode?
StupiduserHH said:
Hi
Could you start the phone in fastboot mode?
Click to expand...
Click to collapse
yes the phone is in fastboot mode, and I cant back to normal mode for regular use.
I tried to unlock again like you said it the program said the device is already unlocked.
Have you tried the first option, wipe data?
Don't panick, since you have fastboot mode it's not bricked. Let's start by booting into TWRP.
Download TWRP and put it in the same directory with your FASTBOOT.exe file.
Open a windows dos prompt and get to the same directory as your FASTBOOT file.
Reboot your phone into FASTBOOT mode.
in your DOS prompt type "Fastboot boot yourrecoveryfilename.img" (change the yourrecoveryfilename.img to the TWRP recovery image file you downloaded)
your phone should reboot into TWRP if there wasn't an error. TWRP won't be permanent (if you reboot out of TWRP it won't retain it), but will allow you to flash ROM.
I've only ever flashed all my ROMs through TWRP, never used anything else since i unlocked the phone.
Let me know how this goes.
fastboot .exe file,where can i get it
_katho_ said:
Have you tried the first option, wipe data?
Click to expand...
Click to collapse
wherecan i download this fastboot file
Hello all.
Big screw up, I think. So I've had my MI 8 for a while now, no issues, until today I decided to install official lineage on it. The bootloader was unlocked. I flashed TWRP, but every time I rebooted the phone, it would go back to stock recovery, not TWRP. So here the issue started:
- Via Mi flash tool, I reflashed global MIUI 10 back to stock. I didn't realize I had relocked the bootloader...
- I tried reflashing TWRP without realizing I had relocked the bootloader.
- Thinking that the TWRP flash was done incorrectly again, I simply wanted to go back to stock, and attempted to use the mi flash tool to reflash, once again, the global stock MIUI 10. the flash tool said it was a success. (I still didn't realize I was on a locked bootloader)
- I am now on a bootloop. I can't get past the stock recovery screen, but I can go into fastboot. The recovery screen has a warning that the ROM cannot be used on the phone.
- I tried re unlocking the bootloader with the unlock tool, but because my Mi account credentials are not input on the phone (the phone was wiped clean), I cannot re unlock it.
What can I do? How can I get out of the bootloop, and hopefully re unlock and flash global rom clean again?
dancarriv said:
Hello all.
Big screw up, I think. So I've had my MI 8 for a while now, no issues, until today I decided to install official lineage on it. The bootloader was unlocked. I flashed TWRP, but every time I rebooted the phone, it would go back to stock recovery, not TWRP. So here the issue started:
- Via Mi flash tool, I reflashed global MIUI 10 back to stock. I didn't realize I had relocked the bootloader...
- I tried reflashing TWRP without realizing I had relocked the bootloader.
- Thinking that the TWRP flash was done incorrectly again, I simply wanted to go back to stock, and attempted to use the mi flash tool to reflash, once again, the global stock MIUI 10. the flash tool said it was a success. (I still didn't realize I was on a locked bootloader)
- I am now on a bootloop. I can't get past the stock recovery screen, but I can go into fastboot. The recovery screen has a warning that the ROM cannot be used on the phone.
- I tried re unlocking the bootloader with the unlock tool, but because my Mi account credentials are not input on the phone (the phone was wiped clean), I cannot re unlock it.
What can I do? How can I get out of the bootloop, and hopefully re unlock and flash global rom clean again?
Click to expand...
Click to collapse
Here I made this thread for you : https://forum.xda-developers.com/mi-8/how-to/how-to-install-roms-resolve-issues-t3911611
tsongming said:
Here I made this thread for you : https://forum.xda-developers.com/mi-8/how-to/how-to-install-roms-resolve-issues-t3911611
Click to expand...
Click to collapse
I finally got around fixing this. It turns out my phone was China, with Global ROM. So I did an EDL test point method and paid someone with an authorized account to access my laptop remotely to Flash the latest China ROM. I waited the required period for bootloader unlocking, and it's back alive!
I'm running official lineage 16, and I'm pretty happy with the results. I'm Using it as a daily driver instead of my all stock pixel 2 XL. No issues.
dancarriv said:
I finally got around fixing this. It turns out my phone was China, with Global ROM. So I did an EDL test point method and paid someone with an authorized account to access my laptop remotely to Flash the latest China ROM. I waited the required period for bootloader unlocking, and it's back alive!
I'm running official lineage 16, and I'm pretty happy with the results. I'm Using it as a daily driver instead of my all stock pixel 2 XL. No issues.
Click to expand...
Click to collapse
That's great news! It sucks that you were tricked into thinking your that phone is a global version. But at least you able to get things permanently sorted.
Sent from my Xiaomi MI 8 using XDA Labs
Agimax said:
Don't panick, since you have fastboot mode it's not bricked. Let's start by booting into TWRP.
Download TWRP and put it in the same directory with your FASTBOOT.exe file.
Open a windows dos prompt and get to the same directory as your FASTBOOT file.
Reboot your phone into FASTBOOT mode.
in your DOS prompt type "Fastboot boot yourrecoveryfilename.img" (change the yourrecoveryfilename.img to the TWRP recovery image file you downloaded)
your phone should reboot into TWRP if there wasn't an error. TWRP won't be permanent (if you reboot out of TWRP it won't retain it), but will allow you to flash ROM.
I've only ever flashed all my ROMs through TWRP, never used anything else since i unlocked the phone.
Let me know how this goes.
Click to expand...
Click to collapse
Hey, so I don't want to spam you, but seems like you really know about this and I desperately need some help...
Could you please take a look at my thread? https://forum.xda-developers.com/xi...nt/help-bricked-mi-mix-2s-installing-t4131269
Thank you

Categories

Resources