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.
So I was trying to get into making a rom and realize how difficult it was so with me being impatient I tried installing the android q gsi straight from google and it works! well kinda Its only showing the android booting screen can anyone get passed it? Im ssure its vey possible
All you need to do is
Flashing the GSI
Reboot to your device’s bootloader using either a button combination or by issuing the command:
adb reboot bootloader
Next, we need to disable Android Verified Boot (AVB). You can do this by entering the following command:
fastboot flash vbmeta vbmeta.img
Next, let’s wipe the system partition:
fastboot erase system (might be easier to do this in twrp)
Boot into twrp:
fastboot boot <img file name>, e.g. fastboot boot twrp.img (use the latest build)
Then drag and drop the system image from zip and twrp image onto the phone and flash the system.img for system and twrp for recovery using twrp
reboot in recovery flash again and wipe data!
done
Gsi Download
https://developer.android.com/preview/gsi-release-notes#downloads * I used the gsm but I dont think it really matters out of the two arms64 I tested both and got the same results
Twrp Download
https://twrp.me/oneplus/oneplus6t.html
NOT trying to click bait i just dont know how to change the title my bad guys
Edit. U also have the VB disable command wrong. What u are saying just flashing the vbmeta. --disable-verification is in there too..
Yeah everyone got that far bud. There is no booting past logo.. we posted about it in a thread last month
fullofhell said:
Edit. U also have the VB disable command wrong. What u are saying just flashing the vbmeta. --disable-verification is in there too..
Yeah everyone got that far bud. There is no booting past logo.. we posted about it in a thread last month
Click to expand...
Click to collapse
Actually I saw on erfran's telegram chat for q gsi someone posted screenshots fully booted into the q gsi that was right away when he first released it too. The guy hasn't respond as to how or what he did differently but if u search for 6t in the chat and scroll all the way up you'll see what I mean. So it's possible hell if theyre getting into the 5 I don't know why we're not able to get in too... Although I'd prefer an official alpha Dev leaked whatever from OnePlus I'd settle for some aosp Google Q
gigilie said:
Actually I saw on erfran's telegram chat for q gsi someone posted screenshots fully booted into the q gsi that was right away when he first released it too. The guy hasn't respond as to how or what he did differently but if u search for 6t in the chat and scroll all the way up you'll see what I mean. So it's possible hell if theyre getting into the 5 I don't know why we're not able to get in too... Although I'd prefer an official alpha Dev leaked whatever from OnePlus I'd settle for some aosp Google Q
Click to expand...
Click to collapse
I have flashed every single gsi he posts on his server. Nothing works on our phone. Non ab stuff has q booting all day. I have even ported his stuff and they still don't boot. Miui is the only thing that works.
@ayjays but the ROM Q beta GSI, work on op6t?
Thanks
@iaio72 yes to a certain extent maybe go off the one plus 6 build I've seen around on the internet I've tried flashing it and it seems to be stuck on the screen before the bootloader but when you check twrp folders have been created like download and music so maybe there's something to it ??*
And @gigilie hopefully he can just boot into twrp, backup, and be generous enough to share ?
So the ROM booted, but don't started? Correct?
I followed your instructions, but the phone doesn't boot
iaio72 said:
So the ROM booted, but don't started? Correct?
Click to expand...
Click to collapse
It has a bootlogo, and that's it.. he never said it went past that. Hence my whole input as stated above. . It doesn't work for us bro. Everyone in tg tried this a month ago. All same results. I managed to port some of it to our stock system img and got a different boot logo...and also the command to disable VB is not the same as flashing the image
It is: fastboot flash --disable-verification vbmeta vbmeta.img
(for the Q gsi the install instructions are to use their vbmeta.img.)
Fastboot flash vbmeta vbmeta.img just flashes vbmeta. U must disable ours and flash theirs. One command
@iaio72 yes it boots but only till you reach Android bootlogo I've tried everything I can't think of anything else that's why I was hoping our talented friends can fix this and @fullofhell I understand this was already brought up I just quickly posted this without doing any further research because I thought I already seen all there was but I'm sure there's a way to make it boots I'm almost certain maybe someone can port with treble or port the boot.img from a pixel build I'm not really an expert just suggesting no reason on giving up cuz someone told me to
ayjays said:
So I was trying to get into making a rom and realize how difficult it was so with me being impatient I tried installing the android q gsi straight from google and it works! well kinda Its only showing the android booting screen can anyone get passed it? Im ssure its vey possible
All you need to do is
Flashing the GSI
Reboot to your device’s bootloader using either a button combination or by issuing the command:
adb reboot bootloader
Next, we need to disable Android Verified Boot (AVB). You can do this by entering the following command:
fastboot flash vbmeta vbmeta.img
Next, let’s wipe the system partition:
fastboot erase system (might be easier to do this in twrp)
Boot into twrp:
fastboot boot <img file name>, e.g. fastboot boot twrp.img (use the latest build)
Then drag and drop the system image from zip and twrp image onto the phone and flash the system.img for system and twrp for recovery using twrp
reboot in recovery flash again and wipe data!
done
Gsi Download
https://developer.android.com/preview/gsi-release-notes#downloads * I used the gsm but I dont think it really matters out of the two arms64 I tested both and got the same results
Twrp Download
https://twrp.me/oneplus/oneplus6t.html
Click to expand...
Click to collapse
Check out this thread. https://forum.xda-developers.com/oneplus-6/development/rom-pixel-3-xl-port-oneplus-6-t3856031
@ayjays this guide can help us to install ANdroid Q DP GSI?
https://forum.xda-developers.com/oneplus-6t/how-to/guide-gsi-flashing-tutorial-one-plus-6t-t3891655
Your a god ??? @sangiman thanks!!
Bit of you guys lol @iaio72
https://forum.xda-developers.com/showpost.php?p=79360784&postcount=286 I think he has found our solution
ayjays said:
https://forum.xda-developers.com/showpost.php?p=79360784&postcount=286 I think he has found our solution
Click to expand...
Click to collapse
Did it boot?
_Masked_ said:
Did it boot?
Click to expand...
Click to collapse
yes it did just make sure you flash international oos 9.0.11 first and oem unlock again then follow his guild for the oneplus 6t its pretty buggy and the wifi doesnt work might not recommend daily use but people can use this to make a rom im sure.. maybe lol
BUT yes its running Q oneplus 6t thank you guys
TWRP Custom Recovery for the Onn Android Tablet series
This is the first fully-featured custom recovery for Walmart's MediaTek-based Onn tablets: ONA19TB002, ONA19TB003 and ONA19TB007. TWRP needs no introduction. If you have come here, you probably have some idea of what it is and what it's used for. This TWRP build does not need the bootloader unlocked or VBMeta verification disabled, although it's recommended that you at least unlock the bootloader.
DISCLAIMER
Everything described in this thread is done at your own risk. No one else will be responsible for any data loss, corruption or damage of your device, including that which results from bugs in this software.
FEATURES
Decrypted data partition
All USB modes functional: MTP, ADB, Mass Storage, OTG, Charging
Fast boot time
Adoptable storage mounting
Firmware image backup and restore
Works under locked bootloader
Android 9 build fits within the 16MB recovery partition -- no compromises or partition resizing necessary
INSTALLATION METHOD 1
Download the recovery to your PC and unzip the image
Unlock the bootloader (skip if you have already done this)
Enable OEM Unlock in Developer Options in Android Settings
Boot into fastboot mode either by holding vol. up+power to power it on and selecting "Fastboot mode", or by running the 'adb reboot bootloader' command from within Android.
Install fastboot and appropriate drivers on your PC if you have not set those up
Unlock the bootloader with the command
Code:
fastboot flashing unlock
...and follow the instructions on the screen. This will wipe your data.
Flash the custom recovery with
Code:
fastboot flash recovery twrp-3.3.1-ONA19TB002.img
(use the right file name path for your device)
Reboot to recovery with
Code:
fastboot oem reboot-recovery
INSTALLATION METHOD 2
This assumes you are familiar with SP Flash Tool or can figure it out on your own
Download the recovery to your PC and unzip the image
Get the appropriate scatter file for your device. The scatter file may be found in the device's firmware under /system/data/misc.
Set up SPFT Download tab as Download Only. Load your scatter file.
Under the recovery line, double-click Location and open your TWRP image.
Click Download and connect your powered-off tablet to your PC. SPFT will automatically flash the recovery to the emmc and disconnect when finished.
INSTALLATION METHOD 3
Head over to Amazing Temp Root for MediaTek ARMv8, read the requirements and directions, and grab the latest mtk-su.
Open a root shell with mtk-su
Flash the (unzipped) recovery with the command:
Code:
dd bs=1048576 if=twrp-3.3.1-0-ONA19TB002.img of=/dev/block/by-name/recovery
(replace the if= file name with your appropriate recovery image path)
Exit root shell
START RECOVERY
Three methods:
On a powered off tablet, hold Vol. up+power for about 3 seconds. In the menu that appears, select "Recovery mode"
With Android ADB, use the command 'adb reboot recovery'
From Android root shell, use the command 'reboot recovery' or just use any root app with OS reboot features
NOTES
Kind of important: Make a backup of your Crypto Footer as soon as you can. This is the encryption key to your data partition. When accessed from TWRP, this key can get "upgraded" so that you will get locked out of Android. TWRP uses a hacky workaround that saves and restores the original footer on every /data decrypt. But that method is not what I would call 100% reliable.
Make sure you have a backup of the untouched stock system and vendor images. There are no official firmware packages available to download.
Only mount system/vendor partitions in read/write mode if you have unlocked the bootloader. It is recommended to choose to leave system read-only at the startup prompt unless you have a specific reason to modify it. If the bootloader is locked, then dm-verity is enforced.* So merely mounting it once in r/w will cause a boot loop.
It's currently not possible to install incremental OTA updates using this TWRP. Use the stock recovery to update the FW. That will only work if you have never mounted system/vendor in write mode.
DOWNLOAD (Nov. 30, 2019)
Current version: 3.3.1-1
ONA19TB002 - Onn 8" model
ONA19TB003 - Onn 10.1" model
ONA19TB007 - Onn 10.1" w/keyboard model
Source code
ONA19TB002 | ONA19TB003 | ONA19TB007
ACKNOWLEDGEMENTS
The team behind TWRP & OmniROM
@tek3195 for testing and feedback on the 8" model
Please post feedback since these are still pretty new and not exhaustively tested. Let me know if I should port it to other models in the series.
Reserved also
grabbing this one too cuz why not
Very nice! I'll download and test the 003 one soon.
I also have a 007 model to experiment with.
I tried about a dozen times to build TWRP and failed miserably LOL. Closest I got was one that would boot but the rotation was all messed up, USB wouldn't work, didn't mount some partitions... Yeah, it was a hot mess.
Do you happen to have sources available?
Hi @NFSP G35,
I'll have the source code soon. Most of the tricks involved patching bootable/recovery. So I need to commit those changes and include the proper patch set from my tree....
Amazing!! Gonna install and test 8" right now.
Has anyone tried a GSI on these tablets yet?
MishaalRahman said:
Has anyone tried a GSI on these tablets yet?
Click to expand...
Click to collapse
I do know @tek3195 , the Onn 8 thread starter, has tried many of them as well as others here, somewhere on that thread he listed his tests and opinion of several of them.
I'm pretty sure others on that thread have also tried GSI's.
MishaalRahman said:
Has anyone tried a GSI on these tablets yet?
Click to expand...
Click to collapse
I did try both Phhuson vanilla and also Liquid Remix (I'm keeping this one for now). I didn't flash them through twrp, but using fastboot via bootloader.
WoW! AwEsOmE! I cannot wait to try this! THANK YOU!!!!!!
Hey,
This is a neat thing to see for the Onn tablets. I have a question though. I own a device based on the mt8163, and am trying to help people with another device I don't own (the powkiddy x18 which also uses the mt8163). One of the things I wanted to do was to make a custom rom for the x18, since it's stock firmware is horrible. And of course, one of the first steps to custom roms is twrp. So I have a question for you that I hope you can answer for me. How did you make this build of twrp? I have seen no device trees for this device so I was kinda curious. If you can help me in any way, I'd be so grateful, and I'm sure the other people with the x18 would be grateful for help.
@diplomatic
Is there a different procedure for installing TWRP on a locked bootloader?
I can confirm that using SP Flash to load your TWRP.img will produce a bootloop when installing to a device with the BL locked. Reflashing the original recovery.img makes the problem go away. You mentioned in the OP that this TWRP will work on a locked BL so I thought I would share my case study with you in following the procedure you defined.
MY SINCERE GRATITUDE FOR YOUR EFFORTS IN PORTING THIS TO THE ONN!
You're welcome, @Spatry.... Can you describe how you ended up with a locked BL? Was it unlocked before? Have you ever tweaked vbmeta? Also, when you say bootloop, do you mean for Android or just for recovery? I'm not going to insist that it works under locked BL. I tested it once and it did boot up...
diplomatic said:
You're welcome, @Spatry.... Can you describe how you ended up with a locked BL? Was it unlocked before? Have you ever tweaked vbmeta? Also, when you say bootloop, do you mean for Android or just for recovery? I'm not going to insist that it works under locked BL. I tested it once and it did boot up...
Click to expand...
Click to collapse
Presently, I am running stock with Magisk patched BOOT on locked bootloader, stock vbmeta. The boot loop was at the ONN Android screen, I could not get it to even boot into recovery.
At one time I did run with the bootloader unlocked (with --disable-verification on stock vbmeta) and I ran Phusson's AOSP, Liquid Remix and Bliss. I found there was no benefit to me in running the other mods so I reverted back to stock courtesy of @CaffeinePizza and the bootloader re-locked to get rid of that annoying 5 second orange state.
In each instance, I always used SP Flash tools to load all .img files. I only used fastboot to install magisk_patched.img onto the stock installation. Unlocking the bootloader erases all data and I did not feel like reinstalling everything again, so I figured I would try to install TWRP per your instruction to see if it would work while the BL was still locked... Restoring the original recovery got rid of the bootloop. I do want to try your TWRP so I will try it with BL unlocked when I get some free time to do so.
Spatry said:
Presently, I am running stock with Magisk patched BOOT on locked bootloader, stock vbmeta. The boot loop was at the ONN Android screen, I could not get it to even boot into recovery.
Click to expand...
Click to collapse
This sounds like you might have flashed a wrong/corrupt image to recovery. It may have to do with AVB checks rather than bootloader lock. But those conditions might be interdependent somehow so I can't tell you for sure. The fact that you are able to boot a patched image on a locked BL says it doesn't care too much about verification. I can tell you for sure that any recovery image must have avb metadata, not necessarily the required hash, for both Android and recovery to boot. Can you try to unzip the image file and flash it over again?
Hmm, the situation with the bootloader lock sounds eerily similar to the Nabi SE. The latter also had a similar implementation where there's not much in the way of locking things down, other than an (easily circumvented) SP Flash Tool signature check and different preloader keys. And here's the real kicker: the nearly-identical Fisher Price Nabi also ran on the MT8163, so it makes me wonder if it's possible to boot Pie on it, or perhaps a GSI assuming that Treble can be tacked onto it.
Also, do you have the source repo to this TWRP port of yours?
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
diplomatic said:
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
Click to expand...
Click to collapse
Where do I find crypto footer to backup
diplomatic said:
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
Click to expand...
Click to collapse
Kinda cool without the ads isn't it. I know I sent one about a week ago or so. I think everybody ought to send you one, you deserve it. THANKS and AWESOME work.
I have two oneplus 6t devices. One which was recently rooted and running kali nethunter flawlessly. I tried to wipe and switch to paranoid android per an xda tutorial. This device after the reset was unable to be flashed with twrp to recovery. Nor will it boot to twrp via fastboot command "fastboot boot "twrp...". I have tried the msm tools and none of which will either recognize the device or the have errors such as 15 second timeouts after connecting and or the "image doesn't match phone!". the drivers have been installed, reinstalled, restarted whatever i could do. Nothing works. I successfully installed and was running PA on one of the devices. Then the mobile network began stopping and starting every second and would not stay steady. I tried a few restarts of the device..... nothing. I looked up everything I could on the issue and couldn't find a thing. After wiping this device and trying to flash twrp to this one as well, I am now in the same boat with both devices.
I now can flash boot_a with an OTA i found but still no twrp support. the phones will both boot and operate correctly with mobile and wifi. But i want them for paranoid android.
I am now on my macbook running parrot OS linux to try and flash from here. I am fairly new to all of this but I've successfully done multiple nexus 5x devices "rooted running nethunter" as well as a oneplus 3t and 7 pro with paranoid android. The 6t is my absolute favorite and I have two of them. I will not give up on them...hahaha.
If anyone has any guidance please help. I'm all for admitting mistakes as well as my lack of experience here. It would have been all me messing things up here somewhere but I feel I have followed intsructions well and used all the tools I can.
Hi there,
Thanks for posting. I found your post when searching online for the exact same issue. Here is what I did to fix the issue on my side:
* If you device display `crash dump mode` without any additional step, press `Vol-Up` + `Power` to shut down gracefully the device
* When the device is shut down, press both buttons `Vol-Up` and `Vol-Down`, the device you reboot in fastboot mode.
* Then reflash the whole device using a fastboot version of the latest ROMS: [link](https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516)
Hope this helps for you as well
@kyle868edward
If you like a good camera I would suggest Pixel Experience or PE+ or PiXeN rom. I'm not knocking AOSPA but camera quality just isn't the same when I've used it even with google camera... If I knew exactly what you did before you experienced this it would help tremendously. Detailed step by step type info.
If I was on stock OOS 10.3.6 on my OnePlus 6t and wanted to flash AOSPA here's what I do:
Boot twrp via fastboot. Nowadays fastboot won't allow me to rename twrp image to twrp.img like it used to. That command fails that way for me now so I just copy and paste the entire name of whatever recovery I'm using over to terminal. That works for me using Ubuntu 18.04.
Boot TWRP
Flash OOS 10.3.6 global from repo in guides section
Flash AOSPA rom
Flash TWRP recovery installer zip
Flash finalize zip
Format data
Reboot system.
That installation process changes slightly depending on whether or not whatever rom I'm installing includes gapps and or twrp but thats how I install roms on my OnePlus 6t. I have a T-Mobile 6t converted to international/global model. If I had a detailed list of exactly what you did I could probably tell what the deal may have been... Hope this helps.
Edit added:
If you are not able to get msm tool to work then that is the end of the road unless you were to do something like send it to get repaired...
Sent from my OnePlus6T using XDA Labs
---------- Post added at 06:00 AM ---------- Previous post was at 05:53 AM ----------
wget said:
Hi there,
Thanks for posting. I found your post when searching online for the exact same issue. Here is what I did to fix the issue on my side:
* If you device display `crash dump mode` without any additional step, press `Vol-Up` + `Power` to shut down gracefully the device
* When the device is shut down, press both buttons `Vol-Up` and `Vol-Down`, the device you reboot in fastboot mode.
* Then reflash the whole device using a fastboot version of the latest ROMS: [link](https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516)
Hope this helps for you as well
Click to expand...
Click to collapse
This is how I've always been able to get out of crash dump on my OnePlus 6t.
I hope power+ volume +&- until it vibrates and says fastboot then hit power on start bootloader screen to reboot system. I've seen crash dumb 13-14 times so far. Only one time this didn't work for me and I went back to crash dump instead of booting system and I always enable developer options and usb debugging immediately after I boot a setup so the time it sent me back to crash dump I just flashed OOS and a rom again and formatted data and booted up.
Sent from my OnePlus6T using XDA Labs
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)