First of all excuse me for my bad english,
i have a opx with stock rom with custom kernel and system partition formated in f2fs
so far so good.
then i wanted to trie the cm12.1 custom rom and installed via twrp and also installed the stock cm12.1 recovery.
i forgot to change partition back to ext4, now the system dont boot.
the problem is that seems that my bootloader is lock again, cant install anything in fastboot because of that.
and can´t install anithing in recovery because is the cm12.1 stock and gives me error.
does anyone knows a zip file that can convert again the system to ext4 flashable in cm12.1 stock recovery.
or a command that can convert system partition back to ext4 in fastboot?
if anyone have any ideias i´m glad to test them.
once again thanks a lot.
Try fastboot erase system
Or fastboot format system
Sent from my ONE E1003 using Tapatalk
loveboy_lion said:
Try fastboot erase system
Or fastboot format system
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
thanks for the tip but didnt work, get the error : Device not unlocked cannot flash or erase
mocas said:
thanks for the tip but didnt work, get the error : Device not unlocked cannot flash or erase
Click to expand...
Click to collapse
cant u just unlock the bootloader
fastboot oem unlock
No, unfortunately I can't. I type the command the phone restarted but stays with locked bootloader.
Enviado do meu SM-N9005 através de Tapatalk
Try to fix it via sideload:
fastboot:
Flash stock recovery first!
adb sideload "img or zip"
marc2040 said:
Try to fix it via sideload:
fastboot:
Flash stock recovery first!
adb sideload "img or zip"
Click to expand...
Click to collapse
still no luck, getting the same errors.
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Ask here if someone can make this work for your device, don't try it.
btw try:
$ fastboot oem device-info
copy and paste the log
Enviado desde mi ONE E1005 mediante Tapatalk
---------- Post added at 07:09 PM ---------- Previous post was at 06:47 PM ----------
I think I found the solution, use MsmDownloadTool. Use a full O+X rom instead.
https://forums.oneplus.net/threads/stuck-in-fastboot-with-locked-boot-loader.104446/page-2
http://forum.xda-developers.com/one...stboot-adb-t2835696/post55024864#post55024864
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
I'm gonna try this tomorrow and make a tutorial if it works.
Enviado desde mi ONE E1005 mediante Tapatalk
ChavitoArg said:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Ask here if someone can make this work for your device, don't try it.
btw try:
$ fastboot oem device-info
copy and paste the log
hi there, thanks
here is the log as you request:
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.058s]
finished. total time: 0.060s
again thanks
Click to expand...
Click to collapse
Related
Hi !
I desesperatly seeking a root process for the Archos Diamond 2 Plus.
I can not find it by google.
As it looks like the P9000 of Elephone, I wondered if it was possible to use its recovery.img and supersu 1 and 2.
An idea ? A link for tutorial or for the stock rom (If root process failed) ?
Please ?
ok, no response.
I have tested with unlocked bootloader procedure but :
- i type adb reboot bootloader
- fastboot oem unlock
An normaly we confirm unlock with vol+ . But with archos diamond 2 plus, wol + is not active. There is no reaction at this moment.
So, if not unlocked bootloder, no flashing..
An idea ?
fanfan7110 said:
ok, no response.
I have tested with unlocked bootloader procedure but :
- i type adb reboot bootloader
- fastboot oem unlock
An normaly we confirm unlock with vol+ . But with archos diamond 2 plus, wol + is not active. There is no reaction at this moment.
So, if not unlocked bootloder, no flashing..
An idea ?
Click to expand...
Click to collapse
What android version?
android 6.0 marshmallow
fanfan7110 said:
android 6.0 marshmallow
Click to expand...
Click to collapse
You can boot into fastboot, which is good, in fastboot, type fastboot oem startftm. It will give you an error in the command line but what this allows you to do, is push files into partitions that are mounted R/W, that is of course, if this actually works for your device since every device is different.
Report results!
So after typed fastboot oem startftm i have the message "FAILED (remote: unknown command)"
And after to trying to put img file in boot , i have this : 'FAILED (remote: download for partition 'boot' is not allowed)"
fanfan7110 said:
So after typed fastboot oem startftm i have the message "FAILED (remote: unknown command)"
And after to trying to put img file in boot , i have this : 'FAILED (remote: download for partition 'boot' is not allowed)"
Click to expand...
Click to collapse
Please please please make a whole IMG backup since what we'll do might brick your device. I can't help you till Thursday, hit me up on Thursday with a reply on this thread.
---------- Post added at 08:51 PM ---------- Previous post was at 08:50 PM ----------
fanfan7110 said:
So after typed fastboot oem startftm i have the message "FAILED (remote: unknown command)"
And after to trying to put img file in boot , i have this : 'FAILED (remote: download for partition 'boot' is not allowed)"
Click to expand...
Click to collapse
Also, it is supposed to say failed when you start it.
hummm i can't take a backup of boot.img, because SU is not installed..
fanfan7110 said:
hummm i can't take a backup of boot.img, because SU is not installed..
Click to expand...
Click to collapse
Well, since the device is running mtk, try this. Flash the superuser binary and report, also, I am NOT responsible for anything, YOU are making these changes.
ok tested, but don't work with marshmallow. MTK Droid tools is incompatible with V6
fanfan7110 said:
ok tested, but don't work with marshmallow. MTK Droid tools is incompatible with V6
Click to expand...
Click to collapse
Well, now you have a mission to somehow port a working recovery to your phone.
Hi all,
Firstly, excuse my english...
I'm in OOS in version 2.1.3 (yea, old) with custom recovery and root. I have followed this guide : http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
I have recently decided to upgrade in OOS 3.x and suprised...... Impossible to boot on TWRP.
$ adb reboot bootloader
Click to expand...
Click to collapse
→ fastboot mode OK
$ sudo fastboot devices
[sudo] Mot de passe de torlik :
4c6f1504 fastboot
Click to expand...
Click to collapse
detected, nice !
$ sudo fastboot boot twrp-2.8.7.0-onyx_f2fs_r9.img
downloading 'boot.img'...
OKAY [ 0.605s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.606s
Click to expand...
Click to collapse
WOOT ?
$ sudo fastboot flash recovery twrp-2.8.7.0-onyx_f2fs_r9.img
target reported max download size of 1073741824 bytes
sending 'recovery' (12130 KB)...
OKAY [ 0.684s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.686s
Click to expand...
Click to collapse
WHAT ?
With VOL- (+) POWER, I boot in Oxygen Recovery, nothing else.
$ sudo fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
Click to expand...
Click to collapse
(bootloader) Device unlocked: false
How my unlock has been lost ? My phone is yet rooted. SuperSu works correctly.
Can you tell me how it is possible to lost twrp ? I have never upgrade since my unlock.
And now, my only solution is to do a 'fastboot oem unlock' and lost my data ?
Thank you
Not sure whats going on there but easy way is to fastboot flash old stock recovery. Then install 3.1.3 with no problems. Rename file and delete .tar .
Your device bootloader is locked.
Why do you want to flash old TWRP.
To install OOS 3.1.3, you should better flash old OOS stock recovery.
But not sure it wil work.
Now, when you try to reboot recovery, on what recovery are you?
Always TWRP? None?
You should flash Oxygen one, so you can try to flash OOS 2.2.3 full rom zip to start.
Kéno40 said:
Your device bootloader is locked.
Why do you want to flash old TWRP.
To install OOS 3.1.3, you should better flash old OOS stock recovery.
But not sure it wil work.
Now, when you try to reboot recovery, on what recovery are you?
Always TWRP? None?
You should flash Oxygen one, so you can try to flash OOS 2.2.3 full rom zip to start.
Click to expand...
Click to collapse
Thanks for answers.
The issue is exactly that:
"Now, when you try to reboot recovery, on what recovery are you?"
I boot on stock recovery... oxygen recovery instead of twrp. Why?? How??
However I had flash my recovery with twrp last months ago and root my phone.
My problem is I do not want to lost my data... Indeed I can unlock again bootloader but all data will be lost.
How could you flash TWRP if your bootloader is locked? :-S
I don't think you ever get re-locked upon any update..
And yes, you probably have to unlock boot and lose all your user data.. Unless you don't have a backup handy of course :I
You can flash oos 3.1.1 through stock recovery no matter if your bootloader locked or unlocked.
Just download the full rom zip of oos 3.1.1 and place this zip in internal storage and flash with stock recovery. After installing oos3.1.1 you can backup your data and after that you have to go to the developer settings and allow the OEM Unlocking and now you can follow same procedure to unlock bootloader.
Hi !
I have a Oneplus X which was using CM13 in the official nightly build. Without any reasons it began to crash all the applications, so I rebooted it.
Then it was keeping rebooting and recompile all the apps.
I tried to sideload the last CM13 update, then the oxygenOS stock rom. I also tried to wipe the partition before to sideload again. Nothing works.
I thought then the cm recovery doesn't have enough features and retry the bootloader flashing with twrp.
Well, basically I don't have the adb permissions and I can't unlock the bootloader in order to flash the recovery as you can see in the code blocks below
Code:
c:\adb>fastboot devices
f54b3af3 fastboot
c:\adb>fastboot oem unlock
...
OKAY [ 0.015s]
finished. total time: 0.016s
c:\adb>adb devices
List of devices attached
f54b3af3 unauthorized
c:\adb>adb reboot bootloader
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
c:\adb>echo "Restarting the device into fastboot manually then..."
"Restarting the device into fastboot manually then..."
c:\adb>fastboot devices
f54b3af3 fastboot
c:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.007s]
finished. total time: 0.007s
c:\adb>
Flash stock firmware,
Stock firmware doesn't require unlocked bootloader
Sent from my Moto G 2014 using XDA-Developers mobile app
---------- Post added at 01:56 PM ---------- Previous post was at 01:53 PM ----------
But why you want adb permission, just fastboot required for unlocking, flashing.
Sent from my Moto G 2014 using XDA-Developers mobile app
Well I tried to install the recovery and the oxygenOS from the official website. It didn't really works, it's the same problem but I don't really know if you consider them as the stock firmware.
So I tried something else to go further. I tried the tuto "[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus X" (I don't have the right to post some links).
The result is not like expected. The phone is keeping booting. The bootloader and the recovery is unreachable.
If I click on "Verify" of the MsmDownloadTool V2.0, I have :
Code:
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_main0.bin: OK
rawprogram0.xml: FAILED
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
persist.img: OK
recovery.img: OK
Any ideas to try ? :/
-- EDIT --
I just find out that I can boot on fastboot mod but the oem is disabled. But there is no way to unlock it by the graphical interface because the phone is in a boot loop.
I found a compromise
Hi guys.
I had to face that my bootloader can't be unlock like some other people. A simple "fastboot oem unlock" doesn't change the unlock bit but it changes the tampered one.
Anyway, I wanted my phone to be operational. With a friend we tried to flash it with MsmDownloaderV2, the qualcomm tool and a lot of different packages. The result was the same : impossible to boot, no recovery avalaible.
Well to go throught this problem, we tried to change the recovery.img of the flashing package with the image given by twrp. It worked, we finally had a recovery working !
Then I tried to reinstall CM13. Without errors messages the installation failed. With a wipe before the installation, at the end, twrp said "No os installed".
I tried to install the last version of OxygenOS. It said that the device was uncompatible even if I downloaded the right version. So I edited the updater-script and updated its hash in the manifest. It doesn't work either because it didn't find the update binary at the correct path even if it was here.
Anyway, I was tired of this sh*t. I tried to install the first version of OxygenOS. It worked.
So now, my phone works with an outdated version. The tamper bit is true while the unlock bit is false, and I have a the last version of twrp for my recovery.
I pass this post in a solved status, but if you have an idea to pass my unlock bit to true or to put an updated version, I will appreciate it
Hi,
I just got this Redmi Note 3 because I wanted a device with good support for LineageOS (I'm tired of Samsung...)
I have the PRO version (with dual SIM) and MIUI Global 8.0 stable (so the codename is KENZO).
I'm following this guide https://wiki.lineageos.org/devices/kenzo/install to get LineageOS up and running.
For my understanding (because I have the "global" MI rom), my bootloader is not locked (but how I can be sure?).
Following the LineageOS installation guide I have installed TWRP and flashed LineageOS + Open GApps ARM64 + LineageOS su addon.
The phone is booting with LineageOS, but I can see nothing apart the boot animation (waited 1 hour, but no luck).
I have tried installing only LineageOS without GApps or su, but with no luck.
I have tried 3 different snapshot of LineageOS with no luck.
Before flashing I clean system/data/cache/dalvik.
What I'm missing?
Thanks for any help or idea :fingers-crossed:
Take a look at this article to find out whether your bootloader is locked or unlocked. If it's locked, I would suggest you unlock it officially, then try installing the ROM from the beginning. Good luck.
jimakos98 said:
Take a look at this article to find out whether your bootloader is locked or unlocked. If it's locked, I would suggest you unlock it officially, then try installing the ROM from the beginning. Good luck.
Click to expand...
Click to collapse
Thank you for the hint.
This is the result of my check (I was guessing correctly, my device appears unlocked).
Code:
# fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
I have also tried the ROM Resurrection Remix, with same result... stuck at boot animation...
Any other ideas?
Thanks! :good:
huntz said:
Thank you for the hint.
This is the result of my check (I was guessing correctly, my device appears unlocked).
Code:
# fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
I have also tried the ROM Resurrection Remix, with same result... stuck at boot animation...
Any other ideas?
Thanks! :good:
Click to expand...
Click to collapse
if your bootloader is unlocked, you're good to go.
(you are getting bootloops because of outdated twrp/firmware)
1. flash official twrp or zcx twrp ( search in the forum)
2. download latest stable firmware+ rom+ gapps
3. if you are using miui, backup your internal storage to pc or otg drive.
4. go to twrp, wipe dalvik+data+system+internal storage
5. after that click "format data"
6. then install firmware+rom+gapps
7. reboot
note: as u format internal storage, u'll need a otg drive to flash rom+gapps. u can also use adb push commands. official unlock is mandatory. if you're not sure your device is unlocked officially or unofficially, u might have to flash miui fastboot rom, then get the permission
Simoom Sadik said:
if your bootloader is unlocked, you're good to go.
(you are getting bootloops because of outdated twrp/firmware)
1. flash official twrp or zcx twrp ( search in the forum)
2. download latest stable firmware+ rom+ gapps
3. if you are using miui, backup your internal storage to pc or otg drive.
4. go to twrp, wipe dalvik+data+system+internal storage
5. after that click "format data"
6. then install firmware+rom+gapps
7. reboot
note: as u format internal storage, u'll need a otg drive to flash rom+gapps. u can also use adb push commands. official unlock is mandatory. if you're not sure your device is unlocked officially or unofficially, u might have to flash miui fastboot rom, then get the permission
Click to expand...
Click to collapse
Before I was not updating the firmware. But this time I have updated also the firmware (with no luck )
I've installed:
twrp-3.1.1-0-kenzo.img
miui_HMNote3ProGlobal_7.9.7_Firmware.zip
lineage-14.1-20170906-nightly-kenzo-signed.zip
open_gapps-arm64-7.1-nano-20170910.zip
addonsu-14.1-arm64-signed.zip
All the ZIP are stored on my SD card; I have also wiped dalvik+data+system+internal storage.
But I'm again stuck on boot animation (for more than 25 min).
meh...
Thank you, anyway
huntz said:
Before I was not updating the firmware. But this time I have updated also the firmware (with no luck )
I've installed:
twrp-3.1.1-0-kenzo.img
miui_HMNote3ProGlobal_7.9.7_Firmware.zip
lineage-14.1-20170906-nightly-kenzo-signed.zip
open_gapps-arm64-7.1-nano-20170910.zip
addonsu-14.1-arm64-signed.zip
All the ZIP are stored on my SD card; I have also wiped dalvik+data+system+internal storage.
But I'm again stuck on boot animation (for more than 25 min).
meh...
Thank you, anyway
Click to expand...
Click to collapse
flash rom+gapps
then flash unlock_bootloader.zip
Simoom Sadik said:
flash rom+gapps
then flash unlock_bootloader.zip
Click to expand...
Click to collapse
:good::good::good:
You are the man!
Thank you.
What I was missing was the unlock_bootloader.zip.
After flashing this file, LineageOS booted in around 3 or 4 minutes.
Thank you, again.
I have the same problem
Simoom Sadik said:
flash rom+gapps
then flash unlock_bootloader.zip
Click to expand...
Click to collapse
Is this zip file lock the bootloader or not because it contains emmc.bin please explain
Joyel said:
Is this zip file lock the bootloader or not because it contains emmc.bin please explain
Click to expand...
Click to collapse
it wont
Can you please provide you unlock details
Simoom Sadik said:
it wont
Click to expand...
Click to collapse
You unlockd your bootloader officially or unofficially.because I am fear to do . I'm unlocked unofficially.any command to unlock the zip
Is this zip lock my bootloader
Simoom Sadik said:
it wont
Click to expand...
Click to collapse
Simoom Sadik said:
flash rom+gapps
then flash unlock_bootloader.zip
Click to expand...
Click to collapse
I'm unofficially unlocked my bootloader.im in lollipop boot loader.flashing this file will lock my bootloader itself or not.thanks in advanc
Joyel said:
Is this zip file lock the bootloader or not because it contains emmc.bin please explain
Click to expand...
Click to collapse
Joyel said:
I'm unofficially unlocked my bootloader.im in lollipop boot loader.flashing this file will lock my bootloader itself or not.thanks in advanc
Click to expand...
Click to collapse
unlock officially then. it's not so hard. and safe
i am officially unlocked. mm bootloader
C:\Android>fastboot devices
317251cf fastboot
C:\Android>fastboot erase data
erasing 'data'...
FAILED (remote: Check device console.)
finished. total time: 0.004s
Hello,
I want to erase data because i can't do this unbrick method (https://forum.xda-developers.com/one...lus-6-t3796665)
despite that it worked before.
(and the Msm recovery don't work)
this problem appeared after many successful uses of the method mentioned above. The problem appeared after wanting to install an older rom on my OP6 for downgrade the play services
I am desperate, I searched for hours and hours on the internet so if a little genius goes through, a little help would not be refused
Awehweh said:
C:\Android>fastboot devices
317251cf fastboot
C:\Android>fastboot erase data
erasing 'data'...
FAILED (remote: Check device console.)
finished. total time: 0.004s
Hello,
I want to erase data because i can't do this unbrick method (https://forum.xda-developers.com/one...lus-6-t3796665)
despite that it worked before.
(and the Msm recovery don't work)
this problem appeared after many successful uses of the method mentioned above. The problem appeared after wanting to install an older rom on my OP6 for downgrade the play services
I am desperate, I searched for hours and hours on the internet so if a little genius goes through, a little help would not be refused
Click to expand...
Click to collapse
Flash a compatible recovery first by dv minimal tools from PC to phone,in fastboot mode,if you cannot enter in twrp
Sent from my LEX820 using Tapatalk
bilausdaniel said:
Flash a compatible recovery first by dv minimal tools from PC to phone,in fastboot mode,if you cannot enter in twrp
Sent from my LEX820 using Tapatalk
Click to expand...
Click to collapse
it dont work, its possible to have recovery stock ?
Awehweh said:
it dont work, its possible to have recovery stock ?
Click to expand...
Click to collapse
Don't know about stock twrp...ask in telegram group.but you tried latest official twrp to flash it by adb in fasboot mode?press volume up and power both time 15 seconds,
Sent from my LEX820 using Tapatalk
bilausdaniel said:
Don't know about stock twrp...ask in telegram group.but you tried latest official twrp to flash it by adb in fasboot mode?press volume up and power both time 15 seconds,
Sent from my LEX820 using Tapatalk
Click to expand...
Click to collapse
yes i already did it