Develop Bugs

HTC M8 gives Encrypted message, Locked boot loader need some serious help....

Hi All,
Thanks for all your continuous efforts. I am in a pickle now. I was using this phone M8 and suddenly something happened.. first it complained about USB charging and then when I rebooted the phone it says the phone is encrypted.. and I never used a password ..no matter whatever i use as password, it says password wrong, reset your phone and when I reset, it gives me the same encryption message. I read on how to power and volume up down button, found that bootloader is locked and I was using the same stock rom, never installed custom recovery
See the attached screenshot and please suggest me if there is any hope of recovering this phone or not.
{
"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"
}
.
Thanks..

na-dev99 said:
Hi All,
Thanks for all your continuous efforts. I am in a pickle now. I was using this phone M8 and suddenly something happened.. first it complained about USB charging and then when I rebooted the phone it says the phone is encrypted.. and I never used a password ..no matter whatever i use as password, it says password wrong, reset your phone and when I reset, it gives me the same encryption message. I read on how to power and volume up down button, found that bootloader is locked and I was using the same stock rom, never installed custom recovery
See the attached screenshot and please suggest me if there is any hope of recovering this phone or not.
Thanks..
Click to expand...
Click to collapse
I am unable load the images..got it now a new member cannot post images.. have to wait for 10 posts atleast

Here is what BootLoader Says:
*** Software Status: Official ***
*** LOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT - 3.19.0.000
radio
OpenDSP
OS- 6.12.1540.4
Nov 27 2015

When I am doing adb devices
It only says " List of Devices Attached " .. but does not show any..
fastboot getvar all returns only < waiting for Device >
Thanks.

Here is another information, not sure how much help it will be:
When I boot the phone, it boots and shows a message:
Your Phone is encrypted
To decrypt your phone, enter your screen lock password.
There are two buttons, decrypt and emergency call
And it says 30 attempts remain before device data is deleted.
But I never used a password, it was just a pattern. No matter what ever i use as a password, it gives a message saying Password incorrect. You data will be wiped, and a Button comes
" reset phone".
I already clicked this reset phone almost 15 times, but it is not doing anything, it says resetting the phone but boots to the above screen showing Phone is Encrypted. And the 30 attempt message is still there.
Thanks

After reading may other thread, I installed the HTC Sync Manager along with drivers.
Installed Fastboot.
Then from boot loader went in to Fastboot.
Now typed "fastboot devices " on command prompt. This time got a result. So i went ahead and got the identifier tokens as per HTCDEV site. Finally got my unlock_code.bin file. Used this file to unlock the bootloader.
The strange thing is the phone came up saying resetting data "Yes" , "No" Option. I selected "Yes", then once it rebooted the same "Encryption Message screen came. I went to the boot loader, it still shows "*** LOCKED***. Did try to run the "fastboot flash unlocktoken Unlock_code.bin" command again and the same thing as above, it is the same result...same locked status..
I do not know what else I can do being a newbie...Please help.

Here is result of
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.1540.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: F**************1
(bootloader) imei: 3*******************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.022s

I don't know much about your problem .. hopefully it is not some hardware problem like the emmc is corrupted.
Have you tried to run a RUU ? RUU will wipes everything on your device and replace it with new image.
If you're willing to try, here is the link for your RUU - http://www.htc.com/us/support/htc-one-m8/news/

ckpv5 said:
I don't know much about your problem .. hopefully it is not some hardware problem like the emmc is corrupted.
Have you tried to run a RUU ? RUU will wipes everything on your device and replace it with new image.
If you're willing to try, here is the link for your RUU - http://www.htc.com/us/support/htc-one-m8/news/
Click to expand...
Click to collapse
Thanks your for the suggestion. I went ahead and downloaded the ROM from HTC website.
Could you please give me instructions how to update from fastboot. My Surface Pro 3 is windows 10. On the HTC Synch Manager it is not recognizing the Phone. But on fastboot from boot loader the command prompt shows me the device. So please show me light.
Thanks.

When you have fastboot working correctly that's good enough. You don't need HTC Sync Manager (please uninstall it .. later after RUUing completed you can reinstall it if you need it)
Make sure you installed the latest HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
Install it to have all the necessary drivers and files needed for RUU to run, uninstall only HTC Sync Manager but leave all other things (don't uninstall them).
Put your device on bootloader/fastboot mode then connect to PC.
Right click the RUU exe and select run as administrator and follow all the instruction - agree, next, next, update, blablabla until it completed.

ckpv5,
I did as you said. I went to boot loader/fastboot. Ran the RUUXXX.exe as admin. It first rebooted the phone and expected it to go to bootloader, but it did not , and finally said usb connection error. Do I have to manually put it in to boot loader each time the phone restarts ? -Thanks

ckpv5, I did extactly as you said. Put the phone on bootloader/fastboot. Started the RUUXXX.exe as Admin. The utility did recognize the phone and rebooted it and the message said, waiting for bootloader. But the phone started the boot to the HTC white screen. The uility said USB is not connected and USB error. Will I be able to manually put the phone to bootloader when it says waiting for boot loader....?

Forgot to mention that you need USB 2.0 and not sure whether your Surface Pro has that. If no, you need to find another PC with USB2.0
It is really late over here (2.40 am).
If you can find a RUU zip for the same version, you can try to install it with external_sd method or fastboot flash it (this should work with USB3.0).
If you can't find one .. I'll tell you how to get one tomorrow as I'm already in bed

I used my surface pro 3 docking station , and changed from usb 3.0 to 2.0 port. But the result is same. waiting for bootloader and then the phone started the boot to the HTC white screen. The utility said USB is not connected and USB error. I tried Fastboot reload-bootloader, it starts booting to the HTC white screen and to the encryption message.
Basically I am seeing that the software is Official, Locked and S-ON. Hboot is 3.19, OS is 6.12.1540.4, Cidnum - BS_US001, product - m8_ul_ca
Let me know if there is any hope for this m8 or not.

here are the screesnhots:
.

na-dev99 said:
I used my surface pro 3 docking station , and changed from usb 3.0 to 2.0 port. But the result is same. waiting for bootloader and then the phone started the boot to the HTC white screen. The utility said USB is not connected and USB error. I tried Fastboot reload-bootloader, it starts booting to the HTC white screen and to the encryption message.
Basically I am seeing that the software is Official, Locked and S-ON. Hboot is 3.19, OS is 6.12.1540.4, Cidnum - BS_US001, product - m8_ul_ca
Let me know if there is any hope for this m8 or not.
Click to expand...
Click to collapse
As I mentioned before, I don't know much about this encryption problem. The only suggestion that I have is to run RUU to replace all the image with stock one but you seems have USB connection problem which usually related to USB3.0
(It will be different approach if you have a TWRP installed where you can simply format (not wipe) data partition to fix it) - running a RUU will format your data partition too (hopefully)
Since you can't try on other PC, do you have a microSD ? If yes, you can try these :
1. Right click your PC start menu and select "run" and type %temp%
2. delete all possible files from this temp folder (some of them you won't be able to delete)
3. Right click the RUU exe and select run as administrator - let it open the agreement and you accept it .. no need to click next or whatever
4. Right click your start menu again and select "run" and type %temp%
5. You'll see two new folders are created - copy out ROM.zip and htc_fastboot.exe from one of those newly created folder (to your desktop)
6. Rename the ROM.zip to 0P6BIMG.zip
7. Put the 0P6BIMG.zip on your microSD root (not in any folder)
8. Put the microSD in your M8
9. When you're at fastboot/bootloader, press power once to go to hboot screen.
10. hboot will scan the 0P6BIMG.img and ask whether you want to update
11. volume up to update and let it run until it say to reboot.
the htc_fastboot.exe is for you to keep for the next method if the above fails.

I tried in another PC as well with USB 2.0 , but when RUU waits for the phone to comeback to bootloader, the phone directly goes to the boot loop. the USB works but only when the phone is in fastboot mode, it is being recognized.
I am ok with data being wiped, i have my contacts , mails, chats etc. are backed up to another phone which I am using now.
I have an SD card , I am going to try your tip as well.
Thanks for this tip, I will do this in evening today. I am in CST, so came out to work.

I followed your instructions and used the 0P6BIMG.zip to an sd card. Under HBOOT it started parsing the file. And after I did the volume up to move on with update, it restarted and from there went to boot loop and showed me the data encryption message. Same behavior as running RUUxxx.exe .
Is there anyway without reboot will I be able to wipe clean from firstboot ?
Thanks.

na-dev99 said:
I followed your instructions and used the 0P6BIMG.zip to an sd card. Under HBOOT it started parsing the file. And after I did the volume up to move on with update, it restarted and from there went to boot loop and showed me the data encryption message. Same behavior as running RUUxxx.exe .
Is there anyway without reboot will I be able to wipe clean from firstboot ?
Thanks.
Click to expand...
Click to collapse
Check this thread. It might shed some light: http://forum.xda-developers.com/showthread.php?t=2749625

joikep said:
Check this thread. It might shed some light: http://forum.xda-developers.com/showthread.php?t=2749625
Click to expand...
Click to collapse
I checked the thread, But the solution has a condition that , BootLoader should be unlocked and the phone should have a custom recovery like TWRP.
Mine is a different case, bootloader locked, S-ON, no custom recovery. Basically the phone is never rooted. Even unlocking the bootloader also takes me to the encryption message and it;s not responding to the unlock token received from htcdev.

HTC One M9 stuck on fastboot bootloader

Hi !
One of my friend ask me to try to save his One M9 phone, that seems to be bricked.
Here is the context :
- I absolutely don't know what he did, and it seems he don't either...
- The phone state is : Software status : Modifed, S-ON, and LOCKED
- I can't have another screen that Fastboot bootloader
The only options in the bootloader menu are :
REBOOT : it works
REBOOT TO BOOTLOADER : it works
BOOT TO DOWNLOAD MODE : does not work (Failed to boot to download mode)
BOOT TO RECOVERY MODE : does not work (Failed to boot to recovery mode)
POWER DOWN : it works
I tried a lt of things, and read a lot of threads before posting this one.
What i can say for the moment is :
- RUU flash using exe : does not work, i get an error saying the battery is too low
- RUU flash using SD card (extract rom.zip, renamed 0PJAIMG.zip, and put on the root of SD card) : zip is not detected at boot
- Getting bootloader unlocked : does not work, because fatboot oem get_token_identifier command seems unknown (probably because oem commands only work in download mode for this phone)
- Getting S-OFF : seems impossible without OS, as it needs Sunshine app installed...
- Few fastboot commands are OK (devices, getvar all, ...) but most of it are refused because of S-ON
- No adb commands are working
Here is the output of fastboot getvar all :
Code:
D:\ANDROID\RUU\RUU>htc_fastboot getvar all
(bootloader) version: 0.5
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno: FA56GYJ01267
all:
finished. total time: 0.094s
htc_fastboot finished. total time: 0.718s
So, from your experts point of view, is this phone definitely bricked, or is there a way to save it ?
Thanks for your precious help guys !

Hey! I have the exact same problem. Anyone knows how to fix that?
I unrooted, stocked and relocked the bootloader. Everything went fine first, was using the phone about two days. But after a restart I'm stuck in bootloader and can't boot to download nor recovery mode.
Phone is only working with fastboot commands.
I also tried these steps OP tried and everything is the same.
I tried to flash hosd file and this works, but still not able to boot to download mode.
The HTC One is an unbranded EU model with 3.35.401.12 (<- but I think there's nothing on the phone right now)

i am also facing same problem with 2 htc one m9 which i have, i also have XTC2CLIP box which is professional tool for all htc devices, i can S-off with this box of all htc phone even no os needed, but phone should accept bootloader mode & ftm mode, & in this case where we can only goto fastboot mode, S-off command not working in state... i spend lot of time but no luck... but i still believe its only software bug & can be solve with fastboot commands. because i aslo read about same problem on htc X model. & they use fastboot command for this problem. but these commands not working on m9 case.

no solution for this? I have one m9 here exatly with the same situation, already did all your debuging with the same results

Hi there! I'm new here, created an account specially for replying to this thread:
So I'm having the same problem, phone (EU M9) died on it's own. Everything is stock.
Tried all of the above, also no results...
Here is my log from "fastboot getvar all"
Code:
C:\Android>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT54NYJ04596
all:
finished. total time: 0.147s
If anyone has any ideas left, I'm happy to try them. For now, it's an ugly paperweight

If it died on its own and in a stock state then you can safely assume it's dead. Most likely nand failure.
Ps, dont all m9 serials start with an "F"?.
Beamed in by telepathy.

thank you

My guess is it tried to do an OTA update overnight, don't know exactly where it went wrong.
By the way, I do get some ADB communication:
First reboot to bootloader (so it doesn't say "Security Warning"), then select 'boot to Recovery Mode' and wait for the red triangle.
If it doesn't reach that point, reboot to bootloader once more. If it does reach the red triangle: hold the Power button and press the Volume Up button once. You can then release the Power button and Recovery Mode should become visible. Note that I tried several options in this menu including "Install from ADB" and "Install from SD Card", but both gave errors.
Hope someone can use this information.

I have exactly this same issue. Sounds like NAND failure? Nothing to be done about it?

KaiLoi said:
I have exactly this same issue. Sounds like NAND failure? Nothing to be done about it?
Click to expand...
Click to collapse
If it's spewing failed to mount errors then yes, dead phone. Only htc will be able to fix it.
Beamed in by telepathy.

Bootloop + can't enter Download or Recovery mode

Hey,
my problem is that, after a reboot, my phone went into a bootloop.
I tried to enter the Recovery or the Download mode but it does not working.
After an automatic restart there is the bootloop again.
I can enter the Bootloader.
Official Software status
Unlocked
S-OFF
an interesting thing is that when i try to read my cid or mid with
fastboot getvar cid/mid
there is nothing to read out. It's empty.
Code:
c:\android>fastboot getvar cid
cid:
finished. total time: 0.036s
c:\android>fastboot getvar mid
mid:
finished. total time: 0.003s

domme0852 said:
Hey,
my problem is that, after a reboot, my phone went into a bootloop.
I tried to enter the Recovery or the Download mode but it does not working.
After an automatic restart there is the bootloop again.
I can enter the Bootloader.
Official Software status
Unlocked
S-OFF
an interesting thing is that when i try to read my cid or mid with
fastboot getvar cid/mid
there is nothing to read out. It's empty.
Click to expand...
Click to collapse
What is the output with fastboot getvar all?

Code:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61b000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:xxxxxxxxxxxx
all:
finished. total time: 0.380s

Since you have access to the bootloader did you try entering recovery from the bootloader itself?...or try using: fastboot reboot recovery, or adb reboot recovery?

I basically have the same problem as you... except my phone is still bootloader locked and s-on. Have you tried putting a 2PS6IMG.zip file (ruu) on the root of a FAT32 formatted microSD card and see if you can access download mode that way?

chrisz5z said:
Since you have access to the bootloader did you try entering recovery from the bootloader itself?...or try using: fastboot reboot recovery, or adb reboot recovery?
Click to expand...
Click to collapse
I tried both. Via bootloader and fastboot command but nothing worked.
adb reboot recovery also doesn't work. There is no devices in adb mode.
Code:
c:\android>adb devices
List of devices attached
c:\android>
mang0 said:
I basically have the same problem as you... except my phone is still bootloader locked and s-on. Have you tried putting a 2PS6IMG.zip file (ruu) on the root of a FAT32 formatted microSD card and see if you can access download mode that way?
Click to expand...
Click to collapse
The download mode is, as I see it, completely bricked. There is no way to enter it.
Without an SDcard it should at least boot into it. But the device is going back to the bootloop.
To answer your question... no I don't try it

domme0852 said:
I tried both. Via bootloader and fastboot command but nothing worked.
adb reboot recovery also doesn't work. There is no devices in adb mode.
Code:
c:\android>adb devices
List of devices attached
c:\android>
The download mode is, as I see it, completely bricked. There is no way to enter it.
Without an SDcard it should at least boot into it. But the device is going back to the bootloop.
To answer your question... no I don't try it
Click to expand...
Click to collapse
You wouldn't be able to see much information via fastboot getvar all unless you were in download mode, so it's not really that strange.
Sometimes you can "trick" (I don't know if that's the correct word) the system into entering download mode from the above method.
At least, from this post and this post, that is what I gathered.

mang0 said:
Sometimes you can "trick" (I don't know if that's the correct word) the system into entering download mode from the above method.
At least, from this post and this post, that is what I gathered.
Click to expand...
Click to collapse
I tried the Method but the Phone still don't want to boot into download mode. It starts the bootloop like before.
I also tried to do an Update via the RUU.exe but this doesn't work too. The program stops with the error low battery although the phone was the whole night on the charger in bootloader. (Don't know if it does not charge right in this state)

Help I have the same problem

Its a simple fix. Take your phone back to carrier or HTC

Bootloader status is still locked even though it says UNLOCKED in Developer Settings.

I'm getting quite desperate right now. I've almost tried everything.
I have enabled OEM Unlocking and USB Debugging in Developer Settings. Mi Unlock Status says it's Unlocked.
I unlocked it in 2019 using Miflash Unlock Tool application when it was still the one where you need to wait a couple days to get approved.
{
"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"
}
Click to expand...
Click to collapse
Then booting to fastboot, running this command: "fastboot oem device-info" shows me this:
Code:
C:\Android\Mi A2 Lite\OTAFlasher fastboot oem device-info
...
[B](bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:[/B]
OKAY [ 0.070s]
finished. total time: 0.071s
I tried using OTAFlasher ADB/Fastboot, Minimal ADB & Fastboot 1.4.3 and using these commands:
Code:
C:\Android\Mi A2 Lite\Minimal fastboot devices
4b09dc1d9905 fastboot
C:\Android\Mi A2 Lite\OTAFlasher fastboot oem edl
...
[B]FAILED (remote: device is locked! no edl)
finished. total time: 0.022s[/B]
C:\Android\Mi A2 Lite\OTAFlasher fastboot flashing unlock
...
[B]FAILED (remote: unknown command)
finished. total time: 0.022s[/B]
C:\Android\Mi A2 Lite\OTAFlasher fastboot oem unlock
...
[B]FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.032s[/B]
C:\Android\Mi A2 Lite\OTAFlasher fastboot oem unlock-go
...
[B]FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.034s
[/B]
Nothing works.
Using MiFlash Unlock application shows me this error: "Couldn't unlock. Please add your account in MIUI's settings Developer options Mi unlock status".
Click to expand...
Click to collapse
And I couldn't add my account because it's only showing this screen (Obviously, because I have unlocked it before):
Click to expand...
Click to collapse
Here's my fastboot getvar all result:
Code:
C:\Android\Mi A2 Lite\OTAFlasher fastboot getvar all
(bootloader) version:0.5
(bootloader) token:VQEBJgEQLS3oiWtLt46mxpFTykTPCAMMc2FrdXJhX2luZGlhAgReP
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3793000
(bootloader) variant:QRD eMMC
(bootloader) unlocked:no
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:MSM8953_DAISY1.0_20180628013533
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1fe00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5d3bfbe00
(bootloader) partition-type:cust:
(bootloader) partition-size:cust: 0x34000000
(bootloader) partition-type:vendor:
(bootloader) partition-size:vendor: 0x40000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) partition-type:oem:
(bootloader) partition-size:oem: 0x10000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:modem:
(bootloader) partition-size:modem: 0x8000000
(bootloader) partition-type:logdump:
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-type:recovery:
(bootloader) partition-size:recovery: 0x4000000
(bootloader) partition-type:boot:
(bootloader) partition-size:boot: 0x4000000
(bootloader) partition-type:persistbak:
(bootloader) partition-size:persistbak: 0x2000000
(bootloader) partition-type:persist:
(bootloader) partition-size:persist: 0x2000000
(bootloader) partition-type:mdtp:
(bootloader) partition-size:mdtp: 0x2000000
(bootloader) partition-type:dsp:
(bootloader) partition-size:dsp: 0x1000000
(bootloader) partition-type:splash:
(bootloader) partition-size:splash: 0x1000000
(bootloader) partition-type:bk5:
(bootloader) partition-size:bk5: 0x800000
(bootloader) partition-type:modemst2:
(bootloader) partition-size:modemst2: 0x800000
(bootloader) partition-type:modemst1:
(bootloader) partition-size:modemst1: 0x800000
(bootloader) partition-type:fsg:
(bootloader) partition-size:fsg: 0x800000
(bootloader) partition-type:devinfo:
(bootloader) partition-size:devinfo: 0x800000
(bootloader) partition-type:mcfg:
(bootloader) partition-size:mcfg: 0x400000
(bootloader) partition-type:tzbak:
(bootloader) partition-size:tzbak: 0x200000
(bootloader) partition-type:tz:
(bootloader) partition-size:tz: 0x200000
(bootloader) partition-type:bk4:
(bootloader) partition-size:bk4: 0x100000
(bootloader) partition-type:dip:
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:abootbak:
(bootloader) partition-size:abootbak: 0x100000
(bootloader) partition-type:aboot:
(bootloader) partition-size:aboot: 0x100000
(bootloader) partition-type:misc:
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-type:keymasterbak:
(bootloader) partition-size:keymasterbak: 0x100000
(bootloader) partition-type:keymaster:
(bootloader) partition-size:keymaster: 0x100000
(bootloader) partition-type:cmnlib64bak:
(bootloader) partition-size:cmnlib64bak: 0x100000
(bootloader) partition-type:cmnlib64:
(bootloader) partition-size:cmnlib64: 0x100000
(bootloader) partition-type:cmnlibbak:
(bootloader) partition-size:cmnlibbak: 0x100000
(bootloader) partition-type:cmnlib:
(bootloader) partition-size:cmnlib: 0x100000
(bootloader) partition-type:syscfg:
(bootloader) partition-size:syscfg: 0x80000
(bootloader) partition-type:keystore:
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:mota:
(bootloader) partition-size:mota: 0x80000
(bootloader) partition-type:rpmbak:
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:sbl1bak:
(bootloader) partition-size:sbl1bak: 0x80000
(bootloader) partition-type:sbl1:
(bootloader) partition-size:sbl1: 0x80000
(bootloader) partition-type:msadp:
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:devcfgbak:
(bootloader) partition-size:devcfgbak: 0x40000
(bootloader) partition-type:devcfg:
(bootloader) partition-size:devcfg: 0x40000
(bootloader) partition-type:lksecappbak:
(bootloader) partition-size:lksecappbak: 0x20000
(bootloader) partition-type:lksecapp:
(bootloader) partition-size:lksecapp: 0x20000
(bootloader) partition-type:bk3:
(bootloader) partition-size:bk3: 0x10000
(bootloader) partition-type:config:
(bootloader) partition-size:config: 0x8000
(bootloader) partition-type:limits:
(bootloader) partition-size:limits: 0x8000
(bootloader) partition-type:DDR:
(bootloader) partition-size:DDR: 0x8000
(bootloader) partition-type:bk2:
(bootloader) partition-size:bk2: 0x5000
(bootloader) partition-type:bk1:
(bootloader) partition-size:bk1: 0x4000
(bootloader) partition-type:sec:
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:dpo:
(bootloader) partition-size:dpo: 0x2000
(bootloader) partition-type:ssd:
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:
(bootloader) partition-size:fsc: 0x2000
(bootloader) rollback_ver:1
(bootloader) serialno:4b09dc1d9905
(bootloader) kernel:lk
(bootloader) product:sakura_india
all:
finished. total time: 1.351s
Any ideas or alternative solutions?
Thank you.

adb, fastboot and "fastboot oem unlock" command

Divolka said:
adb, fastboot and "fastboot oem unlock" command
Click to expand...
Click to collapse
I did. Does not work.

mirzakeehl said:
I did. Does not work.
Click to expand...
Click to collapse
Oh, right didn't see in the post, sorry.
Check if your PC is authorized by your phone, if not sure revoke authorization and authorize again.
Also you might try flashing android one through miflashtool and try to unlock bootloader after that, but I'm pretty sure it requires unlocked bootloader

Divolka said:
Oh, right didn't see in the post, sorry.
Check if your PC is authorized by your phone, if not sure revoke authorization and authorize again.
Also you might try flashing android one through miflashtool and try to unlock bootloader after that, but I'm pretty sure it requires unlocked bootloader
Click to expand...
Click to collapse
Sorry but how do I check if my PC is authorized by my phone?
Using miflashtool doesn't work at all because even though the device is detected, everything results in error. Probably because my bootloader is locked

mirzakeehl said:
Sorry but how do I check if my PC is authorized by my phone?
Using miflashtool doesn't work at all because even though the device is detected, everything results in error. Probably because my bootloader is locked
Click to expand...
Click to collapse
Did you boot to edl? If not you can do that by "adb reboot edl" or "adb oem edl" I never know which one works.
Just revoke all authorization, there option to do that in developer settings, connect to pc and authorize it and try to unlock again

Divolka said:
Did you boot to edl? If not you can do that by "adb reboot edl" or "adb oem edl" I never know which one works.
Just revoke all authorization, there option to do that in developer settings, connect to pc and authorize it and try to unlock again
Click to expand...
Click to collapse
Oh, did you mean USB Debugging authorization? Yeah, I have revoked and authorized it again.
Executing "adb reboot edl" just resets the phone and "adb oem edl" doesn't do anything.
Thanks.

mirzakeehl said:
Oh, did you mean USB Debugging authorization? Yeah, I have revoked and authorized it again.
Executing "adb reboot edl" just resets the phone and "adb oem edl" doesn't do anything.
Thanks.
Click to expand...
Click to collapse
One of those commands, probably first one should make your screen plain black and make notification LED flash

Divolka said:
One of those commands, probably first one should make your screen plain black and make notification LED flash
Click to expand...
Click to collapse
So apparently this phone has a fake UBL and I have to do a flashing by test point to be able to unlock the bootloader. I don't know how to though, do you know how?
Thanks.

mirzakeehl said:
So apparently this phone has a fake UBL and I have to do a flashing by test point to be able to unlock the bootloader. I don't know how to though, do you know how?
Thanks.
Click to expand...
Click to collapse
Sorry but I have no idea, ask on telegram, I'm sure someone will help you on one of all those groups

Divolka said:
Sorry but I have no idea, ask on telegram, I'm sure someone will help you on one of all those groups
Click to expand...
Click to collapse
Will do. Thank you!

mirzakeehl said:
Will do. Thank you!
Click to expand...
Click to collapse
Not sure if this helps but this is how I unlocked my Mi A2 Lite bootloader before then installing Magisk to the phone and a patched boot image:
NB: THe oem unlock and reboot steps where you keep keys pressed BEFORE you enter after the command (this avoids full data wipe of the phone - I can confirm it works!)
USB debug ON
OEm unlock ON
Then connect phone to PC:
adb devices
adb reboot bootloader
fastboot oem unlock - start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
fastboot reboot - start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
Now you are ready to boot into your system. Either boot by holding power button or typing - fastboot reboot - Press Enter
Install Magisk Manager - APK to phone
You need the original boot.img to patch - After you get the boot.img, copy it to the phone memory (via USB or microSD, or download directly from the phone browser, as you prefer).
Open the Magisk Manager app installed previously, it will ask if you want to install Magisk. Accept by tapping on "Install" > "Patch Boot Image File" and select the boot.img file that you have put on phone.
Wait until the process completes (about 1 minute), then tap on "Close". Now in the phone memory, inside the Download directory, you should have a patched_boot.img file. Copy that file to the PC, adbm folder
The original boot image you can get from the fastboot rom using a tool called payload-dumper-win64 (i found it on one of these forums as a download link) - it extracts the image files from the rom
Alternatively, you should be able to download a patched boot image from the A2 Lite forum
adb reboot bootloader
fastboot boot magisk_patched.img
If everything works the phone should boot normally. Open Magisk Manager and it should ask to install Magisk, if not you must tap on the "Install" button.
Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.
Last step to stay safe when a new OTA update arrives: go to "Settings" > "System" > "Developer options" > and disable "Automatic system updates".
When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images" but very important: absolutely don't reboot the phone now!
Important note: Magisk Manager will restore the boot.img that was found on the phone while installing Magisk.
Close Magisk Manager and go to "Settings" > "System" > "System update" and install the OTA update. After the update is downloaded, a two-stages update will begin.
When both stages of the update process completed, it will ask to restart: DON'T DO IT!. Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot (After OTA)" and after that you can tap on "Reboot".
I'm currently on the 11.0.12.0 ROM and the above method works fine - it has for the last 3 monthly OTA updates
Hope this helps

FOREST37 said:
Not sure if this helps but this is how I unlocked my Mi A2 Lite bootloader before then installing Magisk to the phone and a patched boot image:
NB: THe oem unlock and reboot steps where you keep keys pressed BEFORE you enter after the command (this avoids full data wipe of the phone - I can confirm it works!)
USB debug ON
OEm unlock ON
Then connect phone to PC:
adb devices
adb reboot bootloader
fastboot oem unlock - start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
fastboot reboot - start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
Now you are ready to boot into your system. Either boot by holding power button or typing - fastboot reboot - Press Enter
Install Magisk Manager - APK to phone
You need the original boot.img to patch - After you get the boot.img, copy it to the phone memory (via USB or microSD, or download directly from the phone browser, as you prefer).
Open the Magisk Manager app installed previously, it will ask if you want to install Magisk. Accept by tapping on "Install" > "Patch Boot Image File" and select the boot.img file that you have put on phone.
Wait until the process completes (about 1 minute), then tap on "Close". Now in the phone memory, inside the Download directory, you should have a patched_boot.img file. Copy that file to the PC, adbm folder
The original boot image you can get from the fastboot rom using a tool called payload-dumper-win64 (i found it on one of these forums as a download link) - it extracts the image files from the rom
Alternatively, you should be able to download a patched boot image from the A2 Lite forum
adb reboot bootloader
fastboot boot magisk_patched.img
If everything works the phone should boot normally. Open Magisk Manager and it should ask to install Magisk, if not you must tap on the "Install" button.
Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.
Last step to stay safe when a new OTA update arrives: go to "Settings" > "System" > "Developer options" > and disable "Automatic system updates".
When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images" but very important: absolutely don't reboot the phone now!
Important note: Magisk Manager will restore the boot.img that was found on the phone while installing Magisk.
Close Magisk Manager and go to "Settings" > "System" > "System update" and install the OTA update. After the update is downloaded, a two-stages update will begin.
When both stages of the update process completed, it will ask to restart: DON'T DO IT!. Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot (After OTA)" and after that you can tap on "Reboot".
I'm currently on the 11.0.12.0 ROM and the above method works fine - it has for the last 3 monthly OTA updates
Hope this helps
Click to expand...
Click to collapse
First of all, thank you very much for the very detailed guide.
Secondly, do you perhaps still remember what shows up in the CMD/Powershell when you did these commands?
Code:
fastboot oem unlock - start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
fastboot reboot - start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
I assume it showed up as FINISHED without error, right? Unfortunately, mine got stuck right there. Precisely as I've mentioned in the thread's post. So I can't really do the steps after that.
Thanks.

mirzakeehl said:
First of all, thank you very much for the very detailed guide.
Secondly, do you perhaps still remember what shows up in the CMD/Powershell when you did these commands?
Code:
fastboot oem unlock - start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
fastboot reboot - start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
I assume it showed up as FINISHED without error, right? Unfortunately, mine got stuck right there. Precisely as I've mentioned in the thread's post. So I can't really do the steps after that.
Thanks.
Click to expand...
Click to collapse
If I remember correctly I just used abdminimal and it was straightforward, simply entered the command, the phone booted into fastboot mode, typed the next command into the command line, did key combination, pressed enter and it did next stage. Dont think i got anything on the powershell/cmd line such as finished. Sorry, I cant offer any more advice. What happens if you were to toggle the OEM unlocking in the developer options? (apart from possibly wipe your data, would that perhaps reset your phone?) Or perhaps reflash the entire ROM to your phone and start again?

Are you sure you have a Mi A2 Lite (daisy) (Android One) device? Mi A2 Lite does'nt have a MIUI.
I think your phone is Redmi 6 Pro (sakura) or fake 6 Pro made from A2L.
Unlocking Mi A2L is easy by simple command "fastboot oem ulock" nothing more No need request permission to unlock BL in Mi Unlock sw.

lars00 said:
Are you sure you have a Mi A2 Lite (daisy) (Android One) device? Mi A2 Lite does'nt have a MIUI.
I think your phone is Redmi 6 Pro (sakura) or fake 6 Pro made from A2L.
Unlocking Mi A2L is easy by simple command "fastboot oem ulock" nothing more No need request permission to unlock BL in Mi Unlock sw.
Click to expand...
Click to collapse
You're correct. My device is sakura_india. It's a China model with India rom, modified for Indonesia customers.
I've given up, should be easier to just bring the phone to a Xiaomi service center nearby.
Thanks.

mirzakeehl said:
You're correct. My device is sakura_india. It's a China model with India rom, modified for Indonesia customers.
I've given up, should be easier to just bring the phone to a Xiaomi service center nearby.
Thanks.
Click to expand...
Click to collapse
Try "sakura" thread on XDA https://forum.xda-developers.com/redmi-6-pro

The developer option of my phone says that it is unlocked.But when i try to install custom recovery, then my pc says that my phone's bootloader is not unlocked.what should i do?
Please help? What is the problem and how i van get rid of it..
My model:redmi 4 prime (markw)

Question [SOLVED] - Bootloop with completely new OPO9pro after oem unlock

Hello,
just received the phone (EU), updated latest online udpate. (no Google account etc added, just fast setup)
Enabled developer options, OEM unlocking and USB debugging.
After update, 1*reboot.
then another reboot to bootloader, and executed "fastboot oem unlock".
Phone rebooted to recovery. Wiped data, another reboot, now i have only the Red & white dots.....
Any suggestions/hints?
Thanks
Edit:
Entered fastboot mode, did a fastboot oem lock -> same, Red and white dots.

When I unlocked the bootloader I had to wait a much longer time than normal (about 8 minutes) for the dot splash screen to transition to the setup screen and for the phone to boot up fully.
I apologize if this is sort of a "duh I already did that" suggestion. Hope it can help.

Unfortunately not, i waited around 1 hour.
But thanks 4 your comment!

Booting the stock boot.img posted here on XDA -> same result.
Tried to swap the boot slot -> FAILED (remote: Slot Change is not allowed in merging state)
(bootloader) has-slot:system:no
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:3d12cbee
(bootloader) product:lahaina
(bootloader) snapshot-update-status:merging
(bootloader) is-userspace:no
(bootloader) max-download-size:805306368
(bootloader) kernel:uefi
all:
finished. total time: 0.605s

Waiting msm

empty.cad said:
Waiting msm
Click to expand...
Click to collapse
Regarding MSM: if i understood correctly, this is something OPO does not provide, but is "extracted" by some guys here? (key extraction etc??)
So this may take some time.... Probably RTM (cancel order) next week.

yeah once I unlocked BL in fastboot and rebooted, the subsequent next boot took close to 10 minutes, but did boot into a wiped device after

Regarding the error "FAILED (remote: Slot Change is not allowed in merging state)" when swapping the slot, i found tha a
snapshot-update merge — Completes a merge operation, booting to recovery/fastbootd if necessary. This command is valid only if snapshot-update-status is merging, and is only supported in fastbootd.
May help.
But they talk also about
If merging or snapshotted, issue snapshot-update cancel.
But i prefer to ask here before executing, as i have no idea what this does

Well, i could not wait.
After doing a fastboot snapshot-update merge
i rebooted. Same issue.
Booted stock kernel -> issue
Swapped active slot -> Qualcom crash dump
Rebooted to fastboot, oem lock -> phone boots again.
Rebooted twice normally to confirm
Again fastboot oem unlock
Boot fine now. No idea what happened on first oem unlock.

I haven't tried this yet, but I found this link which seems to give a different fastboot command to use. Not sure how much difference it'll make for other users but thought I'd link to it just in case it helps others. I'll probably try it either tomorrow or over the weekend.

I did not use the fastboot oem unlock but the fastboot flashing unlock on the OP9P Global and worked the first time.