Database Info

[SOLVED] Can’t unlock bootloader, can’t boot into the system after he has been unlock

So i have both the short story with some important explanation and the long story on what I've already tried.
Short story
So my dad bought a oneplus one 16GB from someone and the phone has a bootloop when you try the boot into the system.
I tried to unlock the bootloader, but it runned the command and it just reboots to recovery and the bootloader is still locked.
Also the tamperflag is true so that means that the bootloader has already been unlocked and is relocked.
I can't also boot from a custom recovery image because the bootloader is locked (I think it can with CM11S).
Rom: I guess it is CM12S (with the blinking Cyanogen logo at startup).
Recovery: probably the recovery from CM12S (Cyanogen recovery as text and it is a touch recovery).
Long story
So I am going to tell you my story.
My dad bought an oneplus one (16GB) from someone that had a boot loop at startup.
When he told me that I just thought that it was going to be pretty easy to fix: unlock bootloader, flash custom recovery and install a custom rom.
Now, it didn’t roll out as we both expected.
When I unlocked the bootloader it told me after 10 seconds that it was OK.
Pretty weird was that it took so long.
After some research I found that you need to reboot from the rom with adb and that you then can unlock the bootloader. On all my other devices I did that, but now I couldn’t because I wasn’t able to boot inside the rom.
After I “successfully” unlocked the bootloader I did the command “fastboot oem device-info” and it told me that the bootloader was still locked but it was tampered.
I tried after that to boot from a TWRP recovery image but i wasn't able to because the bootloader was locked.
After some research I came at a post on the oneplus forum with a guy that approximately had the same issue except that I can still go into recovery.
I founded this post.
And I first wanted to see if I couldn’t go into recovery and sideload a zip that is signed. That was signed in this thread.
As it expected because I didn’t had a custom recovery it didn’t worked and also I used this tool for adb and fastboot.
I didn’t give up by that one so easily so I tried it with this to sideload the files and I renamed it this time to update.zip. Again as expected an error but this time it was another error.
There came a bunch of errors on the phone especially cache errors and one that said that I had an outdated ADB (at least version 1.0.32).
Weirdly enough I had version 1.0.32 .
And now it tried the trick they told me here.
From the thread for windows 7 and 8 here.
I first did this without “erasing the bootloader”.
I tried this both on windows 8.1 and on windows xp with both administrator rights and I switched between 3 cables each time.
As you see in the attached zip, I correctly installed the driver, this was also the fact for the pc with windows xp.
I also verified the files but there were some that failed (also in the pictures).
It flashes the file 8974_msimage.mbn and then the phone shuts down. I tried this at least three times for each computer.
Then I founded this thread.
And tried this also and exactly the same problem as with color.
Then I tried the same with erasing the bootloader and it had the same issue and I couldn’t erase the bootloader doing to that my partition table doesn’t exist(also in the pictures).
The only thing that I only think that I can do is with a flash tool that uses also the above method but I don’t find any with that I know how to use it.
Any help is appreciated.
Ps: I attached a zip file with some pictures to make it more clear and understandable and i am also dutch, so sorry if my English is bad.

ninjawulf98 said:
So I am going to tell you my story.
My dad bought an oneplus one (16GB) from someone that had a boot loop at startup.
When he told me that I just thought that it was going to be pretty easy to fix: unlock bootloader, flash custom recovery and install a custom rom.
Now, it didn’t roll out as we both expected.
When I unlocked the bootloader it told me after 10 seconds that it was OK.
Pretty weird was that it took so long.
After some research I found that you need to reboot from the rom with adb and that you then can unlock the bootloader. On all my other devices I did that, but now I couldn’t because I wasn’t able to boot inside the rom.
After I “successfully” unlocked the bootloader I did the command “fastboot oem get-lockstate” and it told me that the bootloader was locked but it was tampered.
Sadly enough when I typed the command now it takes forever to answer, after more than 10 minutes it still displays that it is waiting.
After some research I came at a post on the oneplus forum with a guy that approximately had the same issue except that I can still go into recovery.
I founded this post.
And I first wanted to see if I couldn’t go into recovery and sideload a zip that is signed. That was signed in this thread.
As it expected because I didn’t had a custom recovery it didn’t worked and also I used this tool for adb and fastboot.
I didn’t give up by that one so easily so I tried it with this to sideload the files and I renamed it this time to update.zip. Again as expected an error but this time it was another error.
There came a bunch of errors on the phone especially cache errors and one that said that I had an outdated ADB (at least version 1.0.32).
Weirdly enough I had version 1.0.32 .
And now it tried the trick they told me here.
From the thread for windows 7 and 8 here.
I first did this without “erasing the bootloader”.
I tried this both on windows 8.1 and on windows xp with both administrator rights and I switched between 3 cables each time.
As you see in the attached zip, I correctly installed the driver, this was also the fact for the pc with windows xp.
I also verified the files but there were some that failed (also in the pictures).
It flashes the file 8974_msimage.mbn and then the phone shuts down. I tried this at least three times for each computer.
Then I founded this thread.
And tried this also and exactly the same problem as with color.
Then I tried the same with erasing the bootloader and it had the same issue and I couldn’t erase the bootloader doing to that my partition table doesn’t exist(also in the pictures).
The only thing that I only think that I can do is with a flash tool that uses also the above method but I don’t find any with that I know how to use it.
Any help is appreciated.
Ps: I attached a zip file with some pictures to make it more clear and understandable and i am also dutch, so sorry if my English is bad.
Click to expand...
Click to collapse
Are you able to enter fastboot mode now?

Bobbi lim said:
Are you able to enter fastboot mode now?
Click to expand...
Click to collapse
Yes, i can also enter stock recovery but i am unable to boot from custom recovery through fastboot. Because the bootloader is locked.

ninjawulf98 said:
Yes, i can also enter stock recovery but i am unable to boot from custom recovery through fastboot. Because the bootloader is locked.
Click to expand...
Click to collapse
Have you tried "fastboot oem unlock" in fastboot mode?
Sent from my Nexus 7 using Tapatalk

Bobbi lim said:
Have you tried "fastboot oem unlock" in fastboot mode?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes, after - + 10 seconds it says ok and it reboots the phone to the stock recovery.
When i try to flash twrp it just fails because my bootloader is locked.

ninjawulf98 said:
Yes, after - + 10 seconds it says ok and it reboots the phone to the stock recovery.
When i try to flash twrp it just fails because my bootloader is locked.
Click to expand...
Click to collapse
Which stock recovery is it? ColorOS? CM? Or OxygenOS?
I had a similar issue when I tried to unlock mine when I first got my OPO
Sent from my Nexus 7 using Tapatalk

My dad bought the phone from someone and the only thing i can see is cyanogen recovery. At boot i have a blinking cyanogen text. Probably it was already unlocked because the tamper flag is tampered.

ninjawulf98 said:
My dad bought the phone from someone and the only thing i can see is cyanogen recovery. At boot i have a blinking cyanogen text. Probably it was already unlocked because the tamper flag is tampered.
Click to expand...
Click to collapse
Maybe my previous post was a bit confusing but it is still locked, i meant that the previous owner locked it and then relocked it.

Can you tell us the exact copy/paste and output of below command :
fastboot oem device-info
Regards
Girish Sharma

GirishSharma said:
Can you tell us the exact copy/paste and output of below command :
fastboot oem device-info
Regards
Girish Sharma
Click to expand...
Click to collapse
I've got the following:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle rechten voorbehouden.
C:\Windows\System32>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Windows\System32>

I am not sure but, what if you paste the output of fastboot oem unlock from the adb folder, I.e just try to run the command from that directory in which fastboot.exe present. Just paste the output as you done previously.
Regards
Girish Sharma

GirishSharma said:
I am not sure but, what if you paste the output of fastboot oem unlock from the adb folder, I.e just try to run the command from that directory in which fastboot.exe present. Just paste the output as you done previously.
Regards
Girish Sharma
Click to expand...
Click to collapse
Then i've got the following:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
866878f3 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 10.112s]
finished. total time: 10.114s
C:\Program Files (x86)\Minimal ADB and Fastboot>
And when i do the command: "fastboot oem device-info" again.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Program Files (x86)\Minimal ADB and Fastboot>

ninjawulf98 said:
Then i've got the following:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
866878f3 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 10.112s]
finished. total time: 10.114s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
I don't know if this is an issue but i have both the adb and fastboot tools installed from here and the adb, fastboot and drivers here .

Since I am not an android expert, so I shall wait with you to see other member replies. Between if you can check this link too:https://forums.oneplus.net/threads/stuck-in-fastboot-with-locked-boot-loader.104446/page-2
Regards
Girish Sharma

GirishSharma said:
Since I am not an android expert, so I shall wait with you to see other member replies. Between if you can check this link too:https://forums.oneplus.net/threads/stuck-in-fastboot-with-locked-boot-loader.104446/page-2
Regards
Girish Sharma
Click to expand...
Click to collapse
I already founded that thread and did the solution that worked for him and another solution that a guy a few posts above him mentioned. Sadly enough without any results.
Anyway, thanks for the help and all the effort you did!

I just am going to mention it here before I will do it, to avoid to make the situation more worse then it already is.
So you can enter qualcomm hsloader (connect the phone to the pc, press 5-10 seconds volume up + power, screen remains dark).
And there are two tools (which have both the same base) here and here .
Now, when I follow the guide for both tools, always when it flashes the first file (8974_msimage.mbn), after flashing the phone shuts down.
And yes, I gave it administrator rights and the drivers are properly installed.
I tried it also on windows xp (completly clean test computer, yes I have a lot of them )
Now I saw on the oneplus forum a post .
And when I tried the command "fastboot erase bootloader" it gave me the following output:
C:\Windows\System32>fastboot erase bootloader
erasing 'bootloader'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.006s
Well if I try this with the command to erase the kernel partition "fastboot erase boot" I think.
Well might this then work, so that the device after flashing the first file doesn't shutdown?
Again I just want to mention it here before I make the situation more worse then it already is.

ninjawulf98 said:
I just am going to mention it here before I will do it, to avoid to make the situation more worse then it already is.
So you can enter qualcomm hsloader (connect the phone to the pc, press 5-10 seconds volume up + power, screen remains dark).
And there are two tools (which have both the same base) here and here .
Now, when I follow the guide for both tools, always when it flashes the first file (8974_msimage.mbn), after flashing the phone shuts down.
And yes, I gave it administrator rights and the drivers are properly installed.
I tried it also on windows xp (completly clean test computer, yes I have a lot of them )
Now I saw on the oneplus forum a post .
And when I tried the command "fastboot erase bootloader" it gave me the following output:
C:\Windows\System32>fastboot erase bootloader
erasing 'bootloader'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.006s
Well if I try this with the command to erase the kernel partition "fastboot erase boot" I think.
Well might this then work, so that the device after flashing the first file doesn't shutdown?
Again I just want to mention it here before I make the situation more worse then it already is.
Click to expand...
Click to collapse
Now actually i think that the partition bootloader doesn't exists but boot does (which I think containts the bootloader and the kernel).
After waiting very unpationtly -+ 24 hours I tried it.
Sadly enough again without success.
CMD copy:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle rechten voorbehouden.
C:\Windows\System32>fastboot devices
866878f3 fastboot
C:\Windows\System32>fastboot erase boot
erasing 'boot'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.057s
C:\Windows\System32>

Fried emmc. Sell it for junk.
Sent from my SM-G920T

Hi,
I am stuck with a similar issue. Only the way I landed in this situation is slightly different.
Without unlocking the bootloader (I just forgot to do that!), I ran the below command.
Code:
fastboot format cache
It erased the cache but failed to write to it because the device is still locked.
On rebooting, the device was stuck overnight on the "Cyanogen" display screen.
I forcibly powered it off using the power button.
Then I fastbooted it.
Then from the command prompt I tried to run a few commands - see output below
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.031s]
finished. total time: 0.031s
And then this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock oem
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
and this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
That's it. For some reason,"fastboot unlock oem" takes me to fastboot help and "fastboot flashing unlock" just goes in a long endless wait.
Any way out?
Thanks,
Deepak Gupta

Deep.G said:
Hi,
I am stuck with a similar issue. Only the way I landed in this situation is slightly different.
Without unlocking the bootloader (I just forgot to do that!), I ran the below command.
Code:
fastboot format cache
It erased the cache but failed to write to it because the device is still locked.
On rebooting, the device was stuck overnight on the "Cyanogen" display screen.
I forcibly powered it off using the power button.
Then I fastbooted it.
Then from the command prompt I tried to run a few commands - see output below
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.031s]
finished. total time: 0.031s
And then this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock oem
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
and this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
That's it. For some reason,"fastboot unlock oem" takes me to fastboot help and "fastboot flashing unlock" just goes in a long endless wait.
Any way out?
Thanks,
Deepak Gupta
Click to expand...
Click to collapse
The command for unlocking the bootloader is "fastboot oem unlock" not "fastboot unlock oem".
Also sometimes when you type a commando that isn't recognised by the phone it can take forever.
So, I think that the commando "fastboot flashing unlock" doesn't exist.
Anyway I think I know now for sure that the previous owner erased and/or formatted the cache.

6045i - bootloader unlocked but TWRP not flashing

Hi all,
I have a 6045i variant of the idol3. I have successfully unlocked the bootloader and have been trying now to flash TWRP. Then I will install a custom ROM and SU to hopefully end the lagfest.
However, no matter which TWRP I try (2.8.7.0 or 3.0.0-1) it isn't sticking. I've followed the appropriate threads here using adb fastboot to flash the recoveries but when I try to get to recovery it goes to the stock version.
I'm running the latest stock firmware: 5.0.2-7SRN-UEN0
Here's the output of the adb session.
Code:
C:\adb>fastboot -i 0x1bbb devices
cc22eea2 fastboot
C:\adb>fastboot -i 0x1bbb oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Boot cpus: androidboot.earlyboot_cpus=3,4,5,6,7
(bootloader) Big core max freq:
(bootloader) Small core max freq:
OKAY [ 0.028s]
finished. total time: 0.029s
C:\adb>fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img
target reported max download size of 268435456 bytes
sending 'recovery' (23880 KB)...
OKAY [ 0.803s]
writing 'recovery'...
OKAY [ 2.207s]
finished. total time: 3.014s
C:\adb>fastboot -i 0x1bbb reboot
rebooting...
finished. total time: 0.003s
When I invoke recovery (either thru adb or power on/volume up) it loads into stock 3e recovery.
Any tips to get past this? I've done a fair amount of searching for similar issues here but haven't ran into any help.
thanks,

try this:
if youflash the TWRP recovery then turn off the phone and right go to recovery (volume up+power).
If you can go t oTWRP recovery and after reboot yo uwill get the stock one again, then there is a stratup script which replaces the custom recovery with the stock one, on every startup.
You have then to flash the twrp recovry, right boot into it and using the file manager inside TWRP to find the script and delete it.

mikehd1959 said:
Hi all,
I have a 6045i variant of the idol3. I have successfully unlocked the bootloader and have been trying now to flash TWRP. Then I will install a custom ROM and SU to hopefully end the lagfest.
However, no matter which TWRP I try (2.8.7.0 or 3.0.0-1) it isn't sticking. I've followed the appropriate threads here using adb fastboot to flash the recoveries but when I try to get to recovery it goes to the stock version.
I'm running the latest stock firmware: 5.0.2-7SRN-UEN0
Here's the output of the adb session.
Code:
C:\adb>fastboot -i 0x1bbb devices
cc22eea2 fastboot
C:\adb>fastboot -i 0x1bbb oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Boot cpus: androidboot.earlyboot_cpus=3,4,5,6,7
(bootloader) Big core max freq:
(bootloader) Small core max freq:
OKAY [ 0.028s]
finished. total time: 0.029s
C:\adb>fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img
target reported max download size of 268435456 bytes
sending 'recovery' (23880 KB)...
OKAY [ 0.803s]
writing 'recovery'...
OKAY [ 2.207s]
finished. total time: 3.014s
C:\adb>fastboot -i 0x1bbb reboot
rebooting...
finished. total time: 0.003s
When I invoke recovery (either thru adb or power on/volume up) it loads into stock 3e recovery.
Any tips to get past this? I've done a fair amount of searching for similar issues here but haven't ran into any help.
thanks,
Click to expand...
Click to collapse
You can just try like this
Connect to Pc with usb
Open Adb And Fastboot
Enable Debugging on Device
type "adb reboot bootloader"
Then write"fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img"
and then"fastboot -i 0x1bbb boot twrp-3.0.0-1.img"-wait 2s and Automaticily Device will boot to TWRP recovery so you can flash what do you want

Alek Dev said:
You can just try like this
Connect to Pc with usb
Open Adb And Fastboot
Enable Debugging on Device
type "adb reboot bootloader"
Then write"fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img"
and then"fastboot -i 0x1bbb boot twrp-3.0.0-1.img"-wait 2s and Automaticily Device will boot to TWRP recovery so you can flash what do you want
Click to expand...
Click to collapse
Thanks. That's what I just stumbled into as well. I've gotten into TWRP and was able to reboot in TWRP back into TWRP recovery. So now I'm trying reboot to system from TWRP. I'll then reboot to recovery to see if TWRP has stuck.
While in TWRP I used the terminal to find the init scripts. Here's the list:
Code:
init
init.qcom.usb.sh
init.rc
init.recovery.qcom.rc
init.recovery.qcom.usb.rc
When I executed a ls -lh to see timestamps, they were all some default 1969 year. So I didn't muck with anything with init.
Just completed my first boot into the OS. I shut it down fully then restarted with power on + Vol Up and it went straight to TWRP.
So the trick was to do the flash recovery then boot the image as you suggested.
Is this typical for this device? I've never encountered this on other phones (S3 for example).

mikehd1959 said:
Thanks. That's what I just stumbled into as well. I've gotten into TWRP and was able to reboot in TWRP back into TWRP recovery. So now I'm trying reboot to system from TWRP. I'll then reboot to recovery to see if TWRP has stuck.
While in TWRP I used the terminal to find the init scripts. Here's the list:
Code:
init
init.qcom.usb.sh
init.rc
init.recovery.qcom.rc
init.recovery.qcom.usb.rc
When I executed a ls -lh to see timestamps, they were all some default 1969 year. So I didn't muck with anything with init.
Just completed my first boot into the OS. I shut it down fully then restarted with power on + Vol Up and it went straight to TWRP.
So the trick was to do the flash recovery then boot the image as you suggested.
Is this typical for this device? I've never encountered this on other phones (S3 for example).
Click to expand...
Click to collapse
so the trick was been to flash the TWRP recovery and then aumotacilly go to Recovery...and if you want to restart phone...just reboot it .you no need to flash boot

Alek Dev said:
so the trick was been to flash the TWRP recovery and then aumotacilly go to Recovery...and if you want to restart phone...just reboot it .you no need to flash boot
Click to expand...
Click to collapse
Except that didn't work for me. It would consistently go to stock recovery no matter how I tried to exit adb. If I rebooted to recovery in adb the stock recovery would launch. If I plain rebooted to OS and then shut down and restart (power on + Vol Up) it would go to stock recovery. It was only when I did the commands as listed above would it at last go to TWRP and persist across reboots.

mikehd1959 said:
Except that didn't work for me. It would consistently go to stock recovery no matter how I tried to exit adb. If I rebooted to recovery in adb the stock recovery would launch. If I plain rebooted to OS and then shut down and restart (power on + Vol Up) it would go to stock recovery. It was only when I did the commands as listed above would it at last go to TWRP and persist across reboots.
Click to expand...
Click to collapse
So use the commands to go to Twrp..you can try to lock the bootloader and try again to unlock and then flash Twrp..
Edit:So it can be the problem with the system

Alek Dev said:
So use the commands to go to Twrp..you can try to lock the bootloader and try again to unlock and then flash Twrp..
Edit:So it can be the problem with the system
Click to expand...
Click to collapse
No need to do as you describe. It is now working correctly. When I go to recovery, it launches TWRP as expected. Issue closed.

Cannot access system to turn on developer mode

Hi I have been working all day trying to get my moto G up and running again.
The problem is that when I boot it shows the boot animations then boots to a blank screen with backlight on.
So far I have tried.
1. Going into the bootloader then into recovery by holding up for 10s then tapping power. From here I wiped back to factory settings. Then I tired to wipe cach partition. When I did this it said ERASING... then rebooted a second later.
It went back to the same black screen after I booted.
1. Flashing a new recovery. TWERP. The flashing process seemed to go ok ... .
target max-sparse-size: 256MB
sending 'recovery' (9488 KB)...
OKAY [ 0.318s]
writing 'recovery'...
OKAY [ 0.170s]
finished. total time: 0.488s
but when I checked I was still on stock recovery.
Then I went and used fastboot to erase recovery and tried flashing again and rebooted bootloader with fastboot reboot command. Still on stock recovery.
2. Then I tried sideloading falcon to this device it aborted.
3. I discovered the sideload boot recovery and when I was able to load TWERP into RAM and boot from there I thought I had it made.
I tried sideloading my ROM from here and got Error 7 I am on bootloader 4113 and I need to be on a newer on.
4. Flashed bootloader
First with getvar I was able to confirm I was on 13. I downloaded 41.19 and flashed that
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.095s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.099s]
but when I rebooted the bootloader with fastboot reboot, and did getvar again. I saw that I was still on 13.
This is only a short summary of the highlights of what I have tried with this phone today. Can anybody give me and idea how to proceed? I'm stuck fast here.
Then I tried simply booting into TWRP recovery with

And yes I unlocked the bootloader. I also tried flashing a stock ROM from here

I've seen similar reports like yours and no solution. It is supposed to be a hardware error. To confirm this, fastboot boot twrp.img and then run adb shell dmesg > dmesg.txt and post the file, maybe there are any clues in this kernel log.

_that said:
I've seen similar reports like yours and no solution. It is supposed to be a hardware error. To confirm this, fastboot boot twrp.img and then run adb shell dmesg > dmesg.txt and post the file, maybe there are any clues in this kernel log.
Click to expand...
Click to collapse
Sorry. I am not sure exactly how to do this. Would you be so nice as to post command here so that I can cut and paste into command line?

jonawald said:
Sorry. I am not sure exactly how to do this. Would you be so nice as to post command here so that I can cut and paste into command line?
Click to expand...
Click to collapse
You can literally cut and paste the commands from my post (if your twrp image is named "twrp.img"). Between fastboot and adb, wait for TWRP to start up.

_that said:
You can literally cut and paste the commands from my post (if your twrp image is named "twrp.img"). Between fastboot and adb, wait for TWRP to start up.
Click to expand...
Click to collapse
I tried this
adb-mac adb dmesg > dmesg.txt
and this
adb-mac adb shell dmesg > dmesg.txt
I am using a mac as you might guess from the -mac piece. When I try this I get
Android Debug Bridge version 1.0.32
Revision 760a64fe84b7-android
-a - directs adb to listen on all interfaces for a connection
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
etc.

MI4c unlocking hell!

Applied for unlocking at http://en.miui.com/unlock/ and got this:
Apply for unlocking permissions
Sorry, your application has been rejected.
The more active your Mi Account is, the more likely your application will get approved.
Reapply​>>
So no way to get unlock code!
Then tried: https://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
And it seemed to work, could flash TWRP and CM 13.1
Had problems with radio, tried flashing radio, now I'm stuck in fastboot, can't boot to recovery or anything else, loops back to fastboot.
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.062s]
finished. total time: 0.063s​
Any attempt to flash I get: "Partition flashing is not allowed"
Any ideas or should I just enter the "How far can you toss your Xiaomi MI4c contest"?

Your bootloader is re-locked. Follow the unlock procedure again, maybe you flashed the new bootloader.
BTW you don't have to flash the whole rom to change the bootloader, you can just extract it from firmware in zip and run:
fastboot flash aboot emmc_appsboot.mbn

Ydraulikos said:
Your bootloader is re-locked. Follow the unlock procedure again, maybe you flashed the new bootloader.
BTW you don't have to flash the whole rom to change the bootloader, you can just extract it from firmware in zip and run:
fastboot flash aboot emmc_appsboot.mbn
Click to expand...
Click to collapse
Thank you friend Ydraulikos, I have tried flashing boot and recovery before, but I have not tried your version.
Unfortunately this was the result:
C:\adb\images>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (469 KB)...
OKAY [ 0.036s]
writing 'aboot'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 0.083s​

SOLVED!
Things looked pretty hopeless, two days without a phone, but managed to return to MIUI 7.1.6.7 and can proceed from here. I'm not saying this is the righ method, it worked for me and perhaps can help others in a similar situation. Have read a lot of posts in the last two days so please forgive me if I can not give credit to all the people whose advice helped, so thank you xda!
Installed QDLoader HS-USB Driver_64bit_Setup recommended in one of the posts and rechecked my drivers in general.
One command that seemed to be promising was "fastboot oem edl"
However, when my phone went to edl mode it was no longer accessible for fastboot <waiting for device>
On advice of another post I downloaded MiFlash2015.10.28.0 and libra_images_6.1.7_20151221.0000.11_5.1.*.tar.gz
From the command line typed "fastboot oem edl" and with MiFlash flashed MIUI 6.1.7, had to choose the "Flash all except data and storage" option as other options gave me a memory error message. Flashing went okay!
So my phone is back in business now!

Pixel3 Blueline Slot A is dead

It seems my slot A is dead. No matter what I try I cannot boot to it.
I've tried flash.android.com to flash back to stock, even tried going back to Pie, and back to Q, but still Slot A is dead.
With stock Pie I flashed TWRP and tried flashing custom ROM to both slots, but slot A always fails.
Tried sideloading factory OTA and LineageOS, but it keeps failing.
Tried ./flash-all.sh using a few different ROMs, stock and CalyxOS, but it always fails with the following error.
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8537 KB)...
OKAY [ 0.340s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.2-6374987
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.279s]
finished. total time: 0.619s
rebooting into bootloader...
OKAY [ 0.060s]
finished. total time: 0.110s
target reported max download size of 268435456 bytes
sending 'radio_a' (71436 KB)...
OKAY [ 2.050s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00107-200409-B-6382632
(bootloader) Flashing partition modem_a
OKAY [ 0.418s]
finished. total time: 2.467s
rebooting into bootloader...
OKAY [ 0.060s]
finished. total time: 0.110s
extracting android-info.txt (0 MB)...
extracting boot.img (64 MB)...
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB)...
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (787 MB)...
archive does not contain 'system.sig'
extracting system_other.img (152 MB)...
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB)...
archive does not contain 'vbmeta.sig'
extracting vendor.img (440 MB)...
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.2-6374987
Baseband Version.....: g845-00107-200409-B-6382632
Serial Number........: 96KX220PE
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.360s

When slot A is active and I run fastboot flash boot boot.img for installing LineageOS, it will not boot to recovery, but if I set slot B active and do that then recovery works fine.

Do you have the most recent platform tools, and are you definitely launching the ./flash-all from the platform tools folder and not a path referencing an older version (AKA the version of fastboot and ADB that install from apt)?

sliding_billy said:
Do you have the most recent platform tools, and are you definitely launching the ./flash-all from the platform tools folder and not a path referencing an older version (AKA the version of fastboot and ADB that install from apt)?
Click to expand...
Click to collapse
Can you explain how to do that?
What I am doing is downloading the zip file from developer.google.com under Factory Images. Then I unzip that file open the folder and find the flash-all.sh file, open terminal in that folder and run the file using command ./flash-all.sh
Is there a way to run that file from somewhere other than where it is located?

The Lepricon said:
Can you explain how to do that?
What I am doing is downloading the zip file from developer.google.com under Factory Images. Then I unzip that file open the folder and find the flash-all.sh file, open terminal in that folder and run the file using command ./flash-all.sh
Is there a way to run that file from somewhere other than where it is located?
Click to expand...
Click to collapse
Extract the .zip directly into your platform tools folder and then with that folder open right click and open terminal from the folder. That is easier than changing your terminal path and should result in the ./ running directly from that place. Again, be sure you are running the current platform tools.

Hi, I'm not sure if you wrongly wrote the file extension, but shouldn't you run the flash-all.bat instead of the flash-all.sh?

Vanschtezla said:
Hi, I'm not sure if you wrongly wrote the file extension, but shouldn't you run the flash-all.bat instead of the flash-all.sh?
Click to expand...
Click to collapse
Clearly, he is not using Windows (the ./ command in the OP) so .bat file is not relevant.

sliding_billy said:
Clearly, he is not using Windows (the ./ command in the OP) so .bat file is not relevant.
Click to expand...
Click to collapse
I see. Thanks for clarifying that.

I'm running Ubuntu. I also tried Windows and ran the .bat file and got pretty well the same result.
@ sliding_billy I've been pretty busy the last couple days so haven't tried your advice yet. Hoping to get a chance tonight after work.

The Lepricon said:
I'm running Ubuntu. I also tried Windows and ran the .bat file and got pretty well the same result.
@ sliding_billy I've been pretty busy the last couple days so haven't tried your advice yet. Hoping to get a chance tonight after work.
Click to expand...
Click to collapse
One other thing... Have you tried a factory reset from recovery?

sliding_billy said:
One other thing... Have you tried a factory reset from recovery?
Click to expand...
Click to collapse
I believe I have. I'll try that tonight

Ok, so tonight I have tried the following:
Factory reset from recovery - that may have helped. I could then boot to both slots. slot a had lineage, slot b had factory image
unzipped factory image to latest platform tools folder and ran flash-all.sh - still getting same error and still had 2 different ROMs on slots
flashed using flash.android.com from chrome, then set other slot active and flashed again - tried this a few times. whichever slot I have active when I do this boots fine, but the other slot will not boot
So, to summarize, I now have both slots working, but only the slot I flash will boot. So, if I flash slot a, then it will boot, but slot b will not, and vice versa. And, yes I am flashing same ROM to both slots. And, flash-all.sh does not flash to either slot. It just gives met the error I posted in the OP.
Does anyone know why I am getting the error when running flash-all.sh?

The Lepricon said:
Ok, so tonight I have tried the following:
Factory reset from recovery - that may have helped. I could then boot to both slots. slot a had lineage, slot b had factory image
unzipped factory image to latest platform tools folder and ran flash-all.sh - still getting same error and still had 2 different ROMs on slots
flashed using flash.android.com from chrome, then set other slot active and flashed again - tried this a few times. whichever slot I have active when I do this boots fine, but the other slot will not boot
So, to summarize, I now have both slots working, but only the slot I flash will boot. So, if I flash slot a, then it will boot, but slot b will not, and vice versa. And, yes I am flashing same ROM to both slots. And, flash-all.sh does not flash to either slot. It just gives met the error I posted in the OP.
Does anyone know why I am getting the error when running flash-all.sh?
Click to expand...
Click to collapse
I still haven't seen that you are running the current planform tools, so that is my first suggestion. My second one is to sideload the OTA twice (including full boot after of course) so that it will install on both slots and swap. I suspect that you will then have it truly back to normal and can then do a flash-all including the -w to completely wipe.

I downloaded platform-tools_r30.0.4-linux.zip from developer.android.com yesterday and that is what I was using. And it was not working right. So, last night I downloaded it to my Windows machine and tried from there with the same results, only running flash-all.bat.
Late last night I tried your advice of sideloading factory OTA on both slots and that fixed it. Now I can boot to both slots just fine.
Thank you for all your help, sliding_billy

The Lepricon said:
I downloaded platform-tools_r30.0.4-linux.zip from developer.android.com yesterday and that is what I was using. And it was not working right. So, last night I downloaded it to my Windows machine and tried from there with the same results, only running flash-all.bat.
Late last night I tried your advice of sideloading factory OTA on both slots and that fixed it. Now I can boot to both slots just fine.
Thank you for all your help, sliding_billy
Click to expand...
Click to collapse
Great news, and you are quite welcome.