Related
Hi,
Im working on adding the OnePlus 1, 2 and 3 device to the Unified Android Toolkit but need some help as I don't own any of the devices.
If anyone has a device which has not been unlocked or rooted, I need to know the error message displayed in the command prompt when the fastboot oem unlock command is run without enabling oem unlocking in developer options.
I also need a few people who could help test various procedures in the Toolkit. I am modifying the Nexus Toolkit so most things will be the same.
Any help and/or knowledge about the OnePlus devices would be appreciated.
Thanks, Mark.
Questions:
1. Can you fastboot boot on OnePlus devices (fastboot boot boot.img or fastboot boot recovery.img) or does the image need flashing first. I have looked at some root procedures for the OnePlus and they fastboot flash the imge first, then reboot to bootloader and fastboot the image. Im not sure what that is about.
2. Does the standard twrp recovery image work on the OnePlus devices? I have seen a lot of posts where twrp has failed and a different twrp recovery was recommended to fix the problem (which then worked).
3. I need links to all the builds for the OnePlus 1, 2 and 3 devices. Does anyone have these?
4. Does the Universal adb driver pack from koush (CWM) work with the OnePlus? I have found the official drivers made by OnePlus for their devices but I just want to make sure they are the best ones to use. I read that samsung drivers also work.
5. I have been told that the OnePlus devices usb mode does not revert to "charging only" like all the Nexus devices and that adb commands can be sent with the device in MTP mode (Nexus devices need to be switched to PTP to communicate). Can this be confirmed.
I think this is all I need to get a working Toolkit ready within a few days.
Mark.
mskip said:
Questions:
1. Can you fastboot boot on OnePlus devices (fastboot boot boot.img or fastboot boot recovery.img) or does the image need flashing first. I have looked at some root procedures for the OnePlus and they fastboot flash the imge first, then reboot to bootloader and fastboot the image. Im not sure what that is about.
2. Does the standard twrp recovery image work on the OnePlus devices? I have seen a lot of posts where twrp has failed and a different twrp recovery was recommended to fix the problem (which then worked).
3. I need links to all the builds for the OnePlus 1, 2 and 3 devices. Does anyone have these?
4. Does the Universal adb driver pack from koush (CWM) work with the OnePlus? I have found the official drivers made by OnePlus for their devices but I just want to make sure they are the best ones to use. I read that samsung drivers also work.
5. I have been told that the OnePlus devices usb mode does not revert to "charging only" like all the Nexus devices and that adb commands can be sent with the device in MTP mode (Nexus devices need to be switched to PTP to communicate). Can this be confirmed.
I think this is all I need to get a working Toolkit ready within a few days.
Mark.
Click to expand...
Click to collapse
1. Yes,
Code:
fastboot boot boot.img
works.
2. Old firmware needs old TWRP (link) as new firmware needs new TWRP (link).
There is also hybrid recovery which supports both firmware (link) or also this thread which lets you flash right firmware with the good recovery.
3. Thread to official zip and unofficial fastboot files for the Oneplus Two. Here for the Oneplus One. Thanks to @Spannaa. I think mirrors for the Oneplus 3 are actually not available.
4. I don't know.
5. Yes, in MTP, adb commands work. But I think without USB for Marshmallow, the connectivity will go back to Charge only.
mskip is in the house ??
Sent from my ONE A2005 using Tapatalk
Last thing to do is the stock firmware flashing procedure but I think everything else is done.
Does anyone have a OnePlus 1, 2 or 3 and can test any parts of the Toolkit? Main parts to test is driver install, unlock/relock, apk and folder backup and rooting.
Firmware flash procedure should be finished by tomorrow.
Mark.
Hi Mark,
I got a OnePlus 2 with latest OOS 3.0.2
Bootloader unlocked
rooted
TWRP 3.0.2-1
I'm willing to test...
Manuel
castor31 said:
Hi Mark,
I got a OnePlus 2 with latest OOS 3.0.2
Bootloader unlocked
rooted
TWRP 3.0.2-1
I'm willing to test...
Manuel
Click to expand...
Click to collapse
Thanks, what kind of testing can you do?
If you don't want to touch your rom then the basic functions (apk backup, booting to stock/custom recovery) but ideally if you can make a twrp backup or don't mind wiping the device then I need the bootloader unlock, flash stock firmware, rooting, etc tested. If you can do the more in depth testing I can compensate you with a pro code so you can also test the ALLINONE root procedure.
Let me know as the OnePlus 2 main code has been completed and the device modules are being built now.
Mark.
Hi Mark.
OnePlus One with latest COS-13.1-ZNH2KAS1KN
stock
bootloader unlocked
not rooted
twrp backup done
Willing to help with more in depth testing if still needed.
Frank
mskip said:
Thanks, what kind of testing can you do?
If you don't want to touch your rom then the basic functions (apk backup, booting to stock/custom recovery) but ideally if you can make a twrp backup or don't mind wiping the device then I need the bootloader unlock, flash stock firmware, rooting, etc tested. If you can do the more in depth testing I can compensate you with a pro code so you can also test the ALLINONE root procedure.
Let me know as the OnePlus 2 main code has been completed and the device modules are being built now.
Mark.
Click to expand...
Click to collapse
Yes, I can test all this.
I did a dirty flash when the OOS3 community build was released in March. So its time for me to wipe my device and do a clean install...
I'm using your Toolkit with pro for my GNex, n8000 and Nexus5. would be great if you can provide a pro code.
Best
Manuel
UPDATE - TEST RELEASE FOR ONEPLUS DEVICE SUPPORT
I have finished all the work on the OnePlus modules for the 1, 2 and 3 devices and it is ready for testing.
You can download and test the Toolkit from the below link. Please remember that this IS a test version at the moment as I do not own any OnePlus devices but I have checked all the code thoroughly and don't see any problems. I am especially pleased with the unlock/lock routines and will probably implement the code for the Nexus modules if it works well.
Everything can be checked (and please do) except downloading a stock build directly from the Toolkit as I am waiting to hear back from AndroidFileHost to see if I can get direct links to use in the Toolkit. The fastboot flash routines are working though and the Toolkit will detect the storage of the device (16GB or 64GB) and flash the relevant userdata image so you do not have to do that manually anymore.
I have used the Universal USB driver pack from CWM so if anyone has not installed OnePlus drivers yet PLEASE test if this works. I did originally include the official drivers from OnePlus but they close the Toolkit when the drivers installation starts and thats not great.
The ALLINONE routine should work fine and I have sent out some pro codes to testers to check it all works.
All builds are covered and the correct version of TWRP will be downloaded depending on the build selected. Please check everything and let me know of any bugs or textual errors (as I used a lot of the Nexus code) so I can release it publicly as soon as possible.
Download Link: http://skipsoft.net/?wpdmdl=2627
Thanks, Mark.
Frudge1701 said:
Hi Mark.
OnePlus One with latest COS-13.1-ZNH2KAS1KN
stock
bootloader unlocked
not rooted
twrp backup done
Willing to help with more in depth testing if still needed.
Frank
Click to expand...
Click to collapse
Mark- I have the same version on my OnePlus One but unable to unlock the bootloader also. Can you share the procedure to do it. So far, I was trying to use the Toolbox V6 and when I do unlock bootloader in fastboot mode but phone doesnt get detected even. Please help
reply.rathi said:
Mark- I have the same version on my OnePlus One but unable to unlock the bootloader also. Can you share the procedure to do it. So far, I was trying to use the Toolbox V6 and when I do unlock bootloader in fastboot mode but phone doesnt get detected even. Please help
Click to expand...
Click to collapse
Has the bootloader been unlocked before or is this the first time you want to unlock it?
Do you have adb and fastboot drivers installed?
Do you have any knowledge of using adb/fastboot commands in the command prompt?
First thing is to make sure you have the correct drivers installed: http://www.skipsoft.net/?page_id=1302
You can try the Toolkit to see if the bootloader will unlock or I can talk you through the procedure but its a simple command (fastboot oem unlock, or from the toolkit fastboot-toolkit oem unlock).
If it won't unlock you may need to boot to stock recovery and flash a stock image back to your device.
Mark.
Hello everyone
My phone suddenly went into a boot look after multiple process getting stopped.
After that its not booting.
Now it shows the unable to mount E:failed to mount /cache (Invalid argument and i haven't unlocked the boot loader.
please help me with the same.
i have tried wipe cache partition , system reset everything,
If I understand correctly you can't use the official bootloader unlock app because your phone isn't booting android. I'm guessing your recovery is also not working or you would just factory reset the device and boot into android to unlock the bootloader.
I don't know of any unofficial way to unlock the bootloader so if I were you i'd just do it the official way.
1. Download the raw firmware for your device as well as the ASUS Flash Tool.
2. Boot your phone into fastboot and flash it with AFT.
3. Boot your phone into android if you can. If not, at lease your recovery should be working now. Download the latest device firmware form the ASUS website and flash it using the recovery menu of your device. (power + vol down)
4. Boot your phone into android install the bootloader apk.
5. Open bootloader unlocker app to unlock the device (you need to be connected to the internet for this bit)
Raw firmware for your device can be difficult to find but this one worked for me https://ainotech.com/how-to-flash-fi...twrp-recovery/
I am looking for the unofficial method because the official method does not work now.
aeioo said:
I am looking for the unofficial method because the official method does not work now.
Click to expand...
Click to collapse
I am successful this way, Peetama flash official beta rom 6.0.1 raw. After successfully booting back to fastboot to flash twrp. Once done, immediately reboot into twrp. Flash the magisk if necessary. But I went straight to the custom rom viper os 3.1.1 and done.
For details You can read the article here TWRP WITHOUT UBL
frp.a320 said:
I am successful this way, Peetama flash official beta rom 6.0.1 raw. After successfully booting back to fastboot to flash twrp. Once done, immediately reboot into twrp. Flash the magisk if necessary. But I went straight to the custom rom viper os 3.1.1 and done.
For details You can read the article here TWRP WITHOUT UBL
Click to expand...
Click to collapse
You flashed the beta kernel and then flashed TWRP and then switched to custom rom right ?
Did that method from the given link worked for you ?
I flashed the beta rom and then when I booted into the system it said Decryption unsuccessful.. Please help me
Maybe I can provide paid services
Discord - A New Way to Chat with Friends & Communities
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
discord.gg
غر مقفل کر ے میرا بوٹ لوڈر
غیر مقفل کر ے میرا بوٹ لوڈر
غیر مقفل کر یں میرا بوٹ لوڈر
Code:
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Lineage OS 17.1
Properties
Selinux mode : Enforcing
Build type : user
Gapps : not included
LOS recovery : included
Known issues
FM radio
You have to wake up the phone to use the FOD
No charging icon when off
Maybe others you tell me
Installation
I'm not sure about that but you can try :
1 - Download latest stock android 10 ROM from here
2 - Install OrangeFox from here
3 - Set A as active slot, flash stock rom, orangefox installer zip, reboot recovery
4 - Set B as active slot, flash stock rom, orangefox installer zip, reboot recovery again (now you have A10 vendor blobs in both A/B slots)
5 - Flash custom ROM zip
5,5- Maybe factory reset on los recovery
6 - Flash OrangeFox installer
7 - Reboot recovery
8 - Flash Gapps / Magisk(optional)
9 - fastboot format:f2fs userdata
Troubleshoot
If wifi/bluetooth is not working, flash stock dtbo.img with fastboot flash dtbo.img
If ROM keeps rebooting to recovery, format userdata (wipes internal storage!) with fastboot format:f2fs userdata
Downloads
Download 28/03/2020
Checksum : 05a147341c33bf1e04b16bad721d2961
Download 21/03/2020
Checksum : e2fbec3542e8d9c164854103cceb38cf
Telegarm Group
Sources
ROM
Device tree
Kernel
Vendor
Credits
Big thank's to @Golbinex !
LineageOS team - ROM
@Harukey
@prakaship78
@charliespencerchaplin
XDAevDB Information
[ROM][10][UNOFFICIAL] Lineage OS 17.1, ROM for the Xiaomi Mi A3
Contributors
dantir
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: Lineage OS 17.1
Created 2020-03-21
Last Updated 2020-03-28
Changelog
28/03/2020 : FOD fix
23/03/2020 : DO NOT USE THIS BUILD IT DOESN'T BOOT
21/03/2020 : first relase
Nice, will check it out once I get TWRP working again
Plans for official?
amnher said:
Plans for official?
Click to expand...
Click to collapse
I would love to but it's my first rom, I have a lot to learn.
Also I think to be official it must be perfect like no dtbo.img to flash.
fm radio
would there be a way to get fm radio working?
thank you
how to do this (If ROM keeps rebooting to recovery, format userdata (wipes internal storage!) with fastboot format:f2fs userdata)
I just cannot get it to boot, it always leads to a bootloop. I have followed the guide here and here and also installed latest Android 10 fastboot zip to both slots and flashed the twrp-patched boot image to boot to recovery (flashing regular images included in recovery threads will always boot to bootloader) to flash this, it just doesn't boot... Anyone had any luck?
Any way we could have this rom as permissive ?
In order to have gravitybox working we just need permissive selinux ?
vaykossil said:
Any way we could have this rom as permissive ?
In order to have gravitybox working we just need permissive selinux ?
Click to expand...
Click to collapse
Change it, if you use Gravitybox you should know how to root your phone.
Then is easy to change SELinux status, temporaly in a terminal
Code:
setenforce 0
If you want it to stick is better to have a script running at boot with Magisk instead of editing system config files.
The point is if you want permissive mode do it your self, the default state should be Enforced for everyone is a matter of security.
Makishima said:
I just cannot get it to boot, it always leads to a bootloop. I have followed the guide here and here and also installed latest Android 10 fastboot zip to both slots and flashed the twrp-patched boot image to boot to recovery (flashing regular images included in recovery threads will always boot to bootloader) to flash this, it just doesn't boot... Anyone had any luck?
Click to expand...
Click to collapse
me too, I tried different recoverys, different steps but no luck, I just can't get it to boot.
Many thanks for the ROM!
I followed the current installation instructions on the start page (but i did NOT "5,5- Maybe factory reset on los recovery") and the rom seems to work very well (Fingerprint sensor, Bluetooth music box, ...).
After I booted to Lineage OS the first time the android logo appeared two times but then Lineage OS started correctly. I didn't need to flash the dtbo.img.
Initially I also did the step "5,5- Maybe factory reset on los recovery", but when I tried to boot to OrangeFox recovery from fastboot again the bootloader/fastboot screen was launched.
I found one minor issue: When you disable the screen lock then the background image is shifted a little bit for a short time. I also successfully tested data decryption in the provided OrangeFox recovery.
I would be glad if "Signature Spoofing" would be enabled so you can use microG with this rom.
I own the global version of the Mi A3.
facundonak said:
me too, I tried different recoverys, different steps but no luck, I just can't get it to boot.
Click to expand...
Click to collapse
I think you installed 23/03 build. Try the last one : 28/03 It should be better.
FOD works in general, but does it much slower than on stock ROM, and you have to wake up phone first...
Hey dantir,
Thanks for your efforts on this ROM. Been on lineageOS on multiple phones till date. Rooting for you to get this to a more stable state. Kindly request you to not abandon this ROM.
Thanks a lot.
Do magisk modules work well? call recording, busybox, etc ...?
hello
i have bootloop error
before to install lineageos my data partition was encrypted, so i formated it, in order to send via adb the lineageos zip
then i installed lineageos
this command has error :
fastboot format:f2fs userdata
/usr/bin/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
can you confirm we must flash lineageos in orangefox
after installing lineageos must i reboot in fastboot to execute this command : fastboot format:f2fs userdata
hello i installed the rom
how do you create this rom, can you post the instructions
i would like to create a custom rom with my app included as a system app
thnaks
noogpout said:
hello
i have bootloop error
before to install lineageos my data partition was encrypted, so i formated it, in order to send via adb the lineageos zip
then i installed lineageos
this command has error :
fastboot format:f2fs userdata
/usr/bin/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
can you confirm we must flash lineageos in orangefox
after installing lineageos must i reboot in fastboot to execute this command : fastboot format:f2fs userdata
Click to expand...
Click to collapse
Hey! Just use official TWRP (link), works fine with! Did not have to do anything special.
Also, this rom seems stable, gonna start using it as daily driver this weekend I guess. Thanks @dantir, will you keep this updated? You use it as a daily driver too? Any bugs found in the 28th version?
Hi, folks!
I tried install LineageOS but something go wrong and my phone bricked. I read about MSM tool but I'm arch linux user i can't find alternatives for linux. Maybe someone help me figure out. Please don't judge me it's my first expiration with android.
I ran into the same issue when I flashed the OP8 rom over my OP8P tonight (Though not LineageOS), The following article seemed to help out.
[ROM][STOCK][FASTBOOT][OP8P] Stock Fastboot ROMs for OnePlus 8 Pro
Moderator Information This project is not under active development, take precautions when you are installing it. Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via...
forum.xda-developers.com
I personally had to swap to my other slot using `fastboot --set-active=b` then using `fastboot reboot fastboot` to get into fastbootd for most of the commands to work. ( Fastbootd will be listed at the top of the screen )
Hello, im new here, i have a problem with my oneplus 8 pro.
I had and unlocked bootloader and i tried to flash my phone this afternoon with an old boot.img i created by the past when i rooted it without twrp
the phone came into bootloop and entered in recovery mode wich did not help me.
i tried to flash another time the boot.img i created with payload dumper on the last firmware i found on the oneplus website (i had not the original boot.img) but it did not worked, and now its worse
on the screen there is written "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it."
my phone is not even recognized by my computer now;
please help me !
my phone was android 12.1 11c33,
This is a patched boot img from IN2023_C.33. IN2023 is the EU version.
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Please make sure you follow the provided guides around here. Is pretty easy if you follow them and there is a HIGH risk to totally brick your phone if you do something wrong with Android12 firmware files.
Please read this with high attention:
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
thanks you really much for your response and your boot.img
do you know how to make my computer recognize my phone ?
adb said : "waiting for dvice" when i put the line "fastboot flash boot boot.img"
, the phone still says the same message
"The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it."
is there any solution to fix this, thanks you
PS C:\adb> fastboot flash boot boot.img
>>
< waiting for device >
PS C:\adb> "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it."
The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it.
PS C:\adb> fastboot flash boot boot.img
< waiting for device >
Please check the following(If all goes wrong this is the tool you need to safe your device):
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
My device isn't detected when I click on "Enum" button
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
You can also try the following:
Universal ADB Drivers
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
finally i booted with the boot.img you provided me but it did not worked, im now in fastboot mode with bootloop. i will try to unbrick with mSM thanks you
it worked with msm but i lost all. thanks you
stell52 said:
it worked with msm but i lost all. thanks you
Click to expand...
Click to collapse
do you now have a rooted op8pro with IN2023_C.33. EU version or without root? if with root how did you managed it to root? i tried it but with brick and after that i get the op8pro back to life using the msm tool, hut now i have instead of IN2023 EU (BA firmware) version an IN2023 IN (AA firmware) version for some reason...
you can use IN2023 BA with MSM. No its not rooted anymore. i took the eu version with MSM
stell52 said:
you can use IN2023 BA with MSM. No its not rooted anymore. i took the eu version with MSM
Click to expand...
Click to collapse
how did you managed it to use IN2023 BA with msm tool?
xtcislove said:
This is a patched boot img from IN2023_C.33. IN2023 is the EU version.
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Please make sure you follow the provided guides around here. Is pretty easy if you follow them and there is a HIGH risk to totally brick your phone if you do something wrong with Android12 firmware files.
Please read this with high attention:
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Click to expand...
Click to collapse
is this patched with magisk?
xtcislove said:
This is a patched boot img from IN2023_C.33. IN2023 is the EU version.
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Please make sure you follow the provided guides around here. Is pretty easy if you follow them and there is a HIGH risk to totally brick your phone if you do something wrong with Android12 firmware files.
Please read this with high attention:
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, you are my hero! After flashing your boot img, my OP8Pro is finally rooted again and booting (after trying to flash TWRP)