I've been following this guide with the aim of installing lineageos on a 6T I just bought: https://lineageosroms.com/fajita/#installation.
I downloaded the following files in advance:
copy-partitions-20200903_1329.zip
lineage-18.1-20211230-nightly-fajita-signed.zip
lineage-18.1-20211230-recovery-fajita.img
I have followed all the steps up to and including steps 6 of part 'Temporarily booting a custom recovery using fastboot'. The last part that appeared to run successfully was step 5 e.g.: fastboot flash boot lineage-18.1-20211230-recovery-fajita.img
Here is the output of the commands run on the host (serial number redacted):
adb reboot bootloader
➜ fastboot devices
******* fastboot
➜ fastboot oem unlock
OKAY [ 0.036s]
Finished. Total time: 0.036s
➜ adb reboot bootloader
➜ fastboot devices
******** fastboot
➜ fastboot flash lineage-18.1-20211230-recovery-fajita.img
unknown partition 'lineage-18.1-20211230-recovery-fajita.img'
fastboot: error: cannot determine image filename for 'lineage-18.1-20211230-recovery-fajita.img'
➜ fastboot flash boot lineage-18.1-20211230-recovery-fajita.img
Sending 'boot_a' (65536 KB) OKAY [ 1.543s]
Writing 'boot_a' OKAY [ 0.332s]
Finished. Total time: 1.973s
➜ fastboot devices
******** fastboot. ### This is where I just see the message about the OEM being unlocked and integrity.
➜ adb sideload copy-partitions-20200903_1329.zip ## I ran this even though I just saw the integrity message in the hope it would then enable me to select 'Apply Update'.
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
➜ fastboot devices
******** fastboot
NB I once accidentally wrote fastboot flash lineage-18.1-20211230-recovery-fajita.img instead of fastboot flash boot lineage-18.1-20211230-recovery-fajita.img (i.e. I missed off the 'boot'). However, as I got the immediate error "fastboot: error: cannot determine image filename for 'lineage-18.1-20211230-recovery-fajita.img'" I suppose it was a no-op and hopefully didn't do any harm.
The problem is that when I then booted into the phone with volume down and power (step 6) I just got a screen with a message about the OEM being unlocked and phone integrity.
I powered the phone off after waiting a while with volume up and power. Then powered on. Same message. Since then I've tried powering off and on with both volume up and volume down and power. I get into a mode where I can select start, restart boot loader, recovery mode and power off.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As I understood I'm trying to get into 'recovery mode' I selected that, but that just restarts the phone. I think that just took me back to the integrity message and at that point I ran the command adb sideload copy-partitions-20200903_1329.zip in the hope it would bring up the option to apply the update. However, now whenever I restart the phone I don't see the integrity message, just the 'options' menu (please see 'start' option above). I don't see the OEM unlocked/integrity message any more regardless of how I start the phone.
I have now tried basically all the options including restart the bootloader. All lead back to the same screen. When I have the phone connected to my mac via usb, I can still at least see it with fastboot devices:
fastboot devices
******** fastboot
As the guide I'm following doesn't show what you ought to see at each step I'm not sure what should have happened on step 6 when booting into recovery mode (this is my first flash) but as the guide says
'On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.' I'm guessing it should at least have booted into a UI different to the one I'm seeing.
Is there anything I can do now? Should I try flashing another recovery image? Re running anything? Is it 'bricked'?
Really appreciate any guidance.
PS one thing I've noticed is that the instructions of 6T (https://lineageosroms.com/fajita/#installation) say we should run
fastboot flash boot <recovery_filename>.img
whereas the instructions for earlier and later models of the one plus (and other brands) say to run
fastboot flash recovery <recovery_filename>.img
Of course this might be correct, but does anyone know if this is a mistake in the instructions - i.e. should it have been 'recovery' not 'boot' for the 6/6T?
---- EDIT -----
Having looked up some documentation on fastboot (which say the structure of the command is basically fastboot flash <partition> <filename>) and then read around a bit on partitions on Android phones, I'm getting the impression android phones pretty much always have a recovery partition, which would make me think that the 'boot' command is indeed wrong. That said, I've got next to no experience with this so it's hard to be sure that the command isn't correct for some reason I'm not aware of, that only pertains to a few generations of phones.
Anyone?
--- EDIT 2 ----
The maintainers of the wiki.lineageos.org have confirmed to me that the line fastboot flash boot <recovery_filename>.img is written as intended. So still at square one.
Any ideas, anyone?
FWIW I got there. In case it helps anyone to know any of the sordid details, first I flashed back the stock ROM using this thread. Worked pretty much as described albeit I had to unzip the images folder and move the bat file into it so it found the images (first had to get hold of a windows machine).
Once I had it installed again I took an android update on the device. I think it highly likely that this was the cause of the original issue reported above - following the lineageOS wiki would probably have worked from that point, but I never found out as I decided I wanted TWRP anyway and used that as my custom recovery instead. That said, I now realise I could just as well have only installed TWRP after flashing lineage, as flashing LineageOS wiped TWRP.
BTW, I really can't fathom why I either didn't clock or ignored the message about making sure you're on the latest 11 firmware (in a red box!) at the top of the lineageOS install wiki. I don't remember seeing it but perhaps I just thought it would be fine as it was a 'fresh' phone (that had probably lying in a box for a year or so). Anyway, lesson learned.
Had to scramble over some other issues, involving booting a temp 'test' TWRP from crdroid first before flashing the official one, described around this page. I also had an odd 'no system' message in TWRP after wiping the existing system (following these instructions to check which bits to wipe when using TWRP before flashing a custom ROM). Anyone reading might want to check those instructions by asking on a lineageos forum if it makes sense to wipe 'system' on TWRP before flashing the lineage ROM - as I got a message after flashing lineage (in TWRP, before rebooting) that there was no 'system'. However it rebooted (with an error re corrupt user data that I was able to fix just by allowing lineage to wipe the user data again), so it's hard to see how that report of there being no system can have been strictly accurate.
But. I. got. there.
PS now I remember why I didn't see the warning to update the firmware. I was (unknowingly) viewing a repost (on lineageosroms) rather than the original wiki (on wiki.lineageos.org). Beware
i have the same thing but on a newer phone, my pc cant see it so im stuck here for now
Related
EDIT:
Soulution
If you stumble upon this thread while searching for your problem...
There is no specific solution for this problem.
Allthough the phone isn't bricked, you still should do the unbreaking Method 3 in Naman Bhalla's thread on the OnePlus forums (LINK)
The phone is working perfectly again.
Also, if this problem appeared when you tried flashing OOS 3.0, check out this guide.
I did a lot of google research, found a lot of stuff and I'm still stuck at my problem.
Some background information:
I wanted to flash the new Oxygen OS 3.0 Community Build, decided to perform a clean install (full wipe with system, cache, dalvik and data).
Went into TWRP, wiped phone, installed OOS 3.0 - worked.
Made my initial setup, then I wanted to boot into recovery - didn't work.
Then I booted into fastboot, tried fastboot oem unlock, it said:
fastboot oem unlock
...
OKAY [ 0.014s]
finished. total time: 0.014s
Click to expand...
Click to collapse
Afterwards I checked fastboot oem device-info:
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.080s]
finished. total time: 0.080s
Click to expand...
Click to collapse
That means still locked.
The phone won't boot up by itself.
I had to go in fastboot, and then use "fastboot continue" to get into the OS.
At the beginning, I forgot to enable the 'Allow OEM unlock' option in developer settings, it is now enabled but effect remains the same.
My question:
How do I fix my obviously broken recovery? How can I reflash it with a locked bootloader or how do I even unlock the bootloader.
PLEASE do not link me to the unbrick guides - the device is NOT bricked - it boots up with fastboot continue and also shows up as ONE A2003 when connected to pc.
What works:
+ getting into the OS (via fastboot continue)
+ getting into fastboot
What doesn't work:
- unlocking via fastboot oem unlock
- flashing a recovery (device is locked)
- booting into recovery
Thanks in advance for your help & ideas!
Hi man, what a mess did you did
I have been in that situation. (Stock in fastboot/boot logo with bootloader locked and oem unlocking disabled in seetings).
The only thing that worked for me was the naman bahlla tutorial to unbrick hard bricked devices. (The 3rd method).
The link is this one: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Anyway you can ask naman bhalla help in that thread. He will help you.
TS
Tierri said:
Hi man, what a mess did you did
I have been in that situation. (Stock in fastboot/boot logo with bootloader locked and oem unlocking disabled in seetings).
The only thing that worked for me was the naman bahlla tutorial to unbrick hard bricked devices. (The 3rd method).
The link is this one: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Anyway you can ask naman bhalla help in that thread. He will help you.
TS
Click to expand...
Click to collapse
Thanks for your reply.
I've seen the guides from Bhalla, but I don't think that fits for me...
because the device still boots up with a little trick, so apparently only the recovery is broken.
It does not show up as an unknown devices or qualcom device or anyting in device manager.
In fastboot, nothing shows up in Device Manager.
When booted, it shows up normally as ONE A20003
GerRudi said:
Thanks for your reply.
I've seen the guides from Bhalla, but I don't think that fits for me...
because the device still boots up with a little trick, so apparently only the recovery is broken.
It does not show up as an unknown devices or qualcom device or anyting in device manager.
In fastboot, nothing shows up in Device Manager.
When booted, it shows up normally as ONE A20003
Click to expand...
Click to collapse
hum. Ask Naman Bahlla for help.
GerRudi said:
Thanks for your reply.
I've seen the guides from Bhalla, but I don't think that fits for me...
because the device still boots up with a little trick, so apparently only the recovery is broken.
It does not show up as an unknown devices or qualcom device or anyting in device manager.
In fastboot, nothing shows up in Device Manager.
When booted, it shows up normally as ONE A20003
Click to expand...
Click to collapse
When you try to flash a recovery, what error message do you get? Curiosity question.
But I'm gonna have to echo Tierri to use that unbricking method. I get you're not bricked, but that will work to fix your issue. To get the Qualcomm device thing to show in device manager, power down your phone completely. Then connect the USB cable and press VOL UP (don't press power). You should hear the Windows connection chime. Also make sure you're booted up with Windows Device Driver Signature check turned off.
EDIT: I've followed these directions in the past: http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
I did the same thing.
Only way is boot to system (fastboot continue) backup all files from internal memory to pc,
Restore device completly as Tierri said using method 3 unbrick guide.
Unlock bootloader in system (oos 2.2.1 or 2.2.0).
and flash oos 3.0 beta with twrp from that thread: https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
Thanks for all your replies!
As you all suggested, I decided to go through the Bhallas unbricking guide on the OnePlus forums.
This seemed to be the quickest solution out there.
I'll update the Original post with the solution, thanks.
If mods see this, thread can be closed, tagge the thread as solved.
The real op oem fix
follow these steps:
1. launch your cmd
2. plug out your phone
3. power it off
4. power into fastboot
5. plug it into the pc
6. type these commands
"adb start-server"
"fastboot devices" (your device should show in fastboot)
"fastboot oem lock" (this will reboot your phone and reset everything make sure you backup if you need to)
7. skip all OP setup steps(skipping these steps saves your time cause this process will have to be done twice also put into DEV mode and allow usb debugging)
8. once you on your homescreen power off your OP
9. plug it out of the pc
10. put it back into fastboot
11. type these commands before plugging back into pc
"adb kill-server"
"adb start-server"
12. plug it back into the pc and type these commands
"fastboot devices"
"fastboot oem unlock" (sometimes it will prompt you in some kind of asian language asking if you want to reset all your data just click the first option this will also reset your phone again)
that should fix the OEM boot unlocker now
i made this solution my self after troubleshooting like crazzy cause i had the same problem like you but didnt have to do all the extra bs with download random crap that does not really help
~xjinx216
is your bootloader unlocked now after following naman's process? please help, i've been having the same problem for ages.
I'm having this issue as well. Tried every driver and just can't seem to unlock bootloader. Adb seems to work, can boot into fastboot but then it always says fastboot cannot be detected when I try anything. Or it gets stuck on waiting for device. I just want to get this thing rooted????
Im having the same issue and my device IS bricked (and im sure i may have somehow deleted my OS) And i can't do anything to fix it, but if i deleted/corrupted my OS can it still be oem locked?
Solution
GerRudi said:
EDIT:
Soulution
If you stumble upon this thread while searching for your problem...
There is no specific solution for this problem.
Allthough the phone isn't bricked, you still should do the unbreaking Method 3 in Naman Bhalla's thread on the OnePlus forums (LINK)
Click to expand...
Click to collapse
I had about the same problems with my phone (oem unlock shows okay but doesn't unlock, directly booted the not working recovery) i was then able to boot to system with "fastboot continue".
Solution i found (root needed): flash stock recovery (from oneplus 2 downloads section) in rom with "dd" command and do a oem unlock, it will then boot to stock recovery, where you have to confirm the unlock (works with all roms but only with stock recovery).
command used to flash recovery (in android terminal emulator, adb should work too): dd if="location of recovery.img to flash" of=/dev/block/bootdevice/by-name/recovery
You can also flash twrp on a locked bootloader like this (just make sure to have a stock recovery ready on the device).
You might want to include this in front page.
GerRudi said:
EDIT:
What works:
+ getting into the OS (via fastboot continue)
+ getting into fastboot
What doesn't work:
- unlocking via fastboot oem unlock
- flashing a recovery (device is locked)
- booting into recovery
Click to expand...
Click to collapse
I got into exactly the same situation now, the problem is that "Method 3 in Naman Bhalla's thread" is not working for me as it break on "sahara error". Actually the message says to restart phone and retry, but I'm always getting into this error again and again. I already tried to reinstall drivers many times and I'm running in testing mode... what else I can try to solve this? (Windows 10 Pro)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
My phones memory was full and I didn't care much because I was really busy with other things in life. So i was moving away time to clean it up and flash another rom on it because the stock rom is a pain in the arsch.
Now my phone stays in a bootloop for almost 2 hours, already cleared cache. It loops until it shows "optimizing apps".
Is there any way to recovery a few photo's from my devices? I have not made a recent backup of a few photo's. I feel so bad now... It really sucks
So I got my phone to be detected after several bootloops when it starts the android OS and is "optimizing apps"..
So I quickly did adb reboot botloader
@ Echo off
adb reboot bootloader
fastboot -i 0x2b4c boot twrp.img
echo booting TWRP
pause >nul
And it now shows me :
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.328s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.343s
booting TWRP
Edit.. I am ****ed over now?
< waiting for device >
...
FAILED (remote: oem unlock is not allowed)
finished. total time: -0.000s
downloading 'boot.img'...
OKAY [ 0.320s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.320s
booting TWRP
Bootloader is locked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ffs
Edit2:
my last idea and last hope for recovery is,
bootloop until "Android is being started, App x of x optimizing.."
open adb shell
push my fresh boot.img to the root direcotory
reboot to bootloader
open recovery
flash and hope for the best
all the files are still on the device, if I do adb shell I can see all files.. if this doesn't work I will have to do it manually !! x_x
NiTrOwow said:
Hi,
My phones memory was full and I didn't care much because I was really busy with other things in life. So i was moving away time to clean it up and flash another rom on it because the stock rom is a pain in the arsch.
Now my phone stays in a bootloop for almost 2 hours, already cleared cache. It looops until it shows "optimizing apps".
Is there any way to recovery a few phones from my devices? I have not made a recent backup of a few photo's. I feel so bad now... It really sucks
Click to expand...
Click to collapse
Seems you dirty flashed a new ROM over your actually rom which isn't the same as before. You can try to flashing the same rom within twrp again again.
strongst said:
Seems you dirty flashed a new ROM over your actually rom which isn't the same as before.
Click to expand...
Click to collapse
The bootloader is locked, and the Android rom is original. So this means your answer is not right.
I think the nandflash memory on the system partition went bad, when I go in recovery and look in the recovery log it shows me several blocks have been moved. I can't read or copy all of it to look carefully at it, but I still have adb shell access so there's a small chance to recovery a few photo's and call it a day (I hope).
I think I will buy the same model again and this time unlock the bootloader, flash a custom rom on it and keep regular backups (always good to do anyways).
PS the Android version I had on it was COS 12.1 from Lenovo itself.
NiTrOwow said:
The bootloader is locked, and the android rom is original. So this means your answer is not right.
I think the nandflash memory on the system partition went bad, when I go in recovery and look in the recovery log it shows me several blocks have been moved. I can't read or copy all of it to look carefully at it, but I still have adb shell access so there's a small chance to recovery a few photo's and call it a day (I hope).
I think I will buy the same model again and this time unlock the bootloader, flash a custom rom on it and keep regular updates.
Click to expand...
Click to collapse
I just give some thoughts based on your input
Save your pics and try to flash the stock rom again so the partition will be rewritten and see if there are really nand problems.
strongst said:
I just give some thoughts based on your input
Save your pics and try to flash the stock rom again so the partition will be rewritten and see if there are really nand problems.
Click to expand...
Click to collapse
Yes, I have tried this.
I got my hands on the shell, after a few reboots with a authorized machine (my Android dev VM).
So i had shell I did cat /system/build.prop
I verified that I had the same rom .zip. So I went intro recovery mode and did a ADB sideload. It failed somehow, because nothing changed.
The bootloader is locked too, I can't try a custom recovery like TWRP or others. I tried, but it gave me a error (see post 2).
So my last hope was do to lots of reboots until I gain adb shell access again. I did this, I tried to push the rom zip (700mb) to /sdcard. But before the transfer was complete the phone crashed again.
Maybe I can push two parts splitted in half and then rejoin them again and install it from recovery. If this doesn't work my last resort is to do recovery by shell, e.g list dirs, and pull the files I need (painful and a lot of work..)
I got lucky.. It worked, it now runs my ****ty script to scrape all missing files from the phone that I was missing in my last backup (also lots of bs like you see in the image below)..
RIP!
DISCLAIMER:
take care, this will erase all data on phone. I'm not responsible for any data loss. Follow the instructions on your own risk!
---------------------------------------
You updated to ZUI 3.5 using https://forum.xda-developers.com/zu...-to-zui-z2-t3928693/post79493369#post79493369 ? Congrats!
Once you updated to ZUI 3.5 you don't need to get unlock_bootloader.img anymore.
To activate developer option click 7 times on ZUI version under settings - system - about:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-
-
Once you did that you get developer options in settings - system:
Click on it and activate the options OEM unlocking and USB debugging
You can accept the following warning:
Now:
Setup ADB and Fastboot on your PC. (can be found here as well: https://forum.xda-developers.com/showthread.php?t=2317790)
Connect your Lenovo ZUK phone to the PC.
└ If you get a prompt on phone’s screen to Allow USB debugging, tap OK.
Open a command window inside the folder where you saved your adb and fastboot install (I suggest using C:\ZUK). To do this, open the folder and then “Shift + Right click” on any empty white-space inside the folder and select “Open command window here” from the context menu.
Once command window is open, issue the following command to boot device into bootloader mode:
adb reboot bootloader
Once in bootloader mode, issue the following command to unlock the device:
fastboot -i 0x2b4c oem unlock-go
└ You’ll see the following output:
...
OKAY [ 0.041s]
finished. total time: 0.041s
Now phone will reboot. Let the reboot finish completely. Then do "adb reboot bootloader" again.
now flashing twrp. Download latest twrp version here: https://twrp.me/zuk/zukz2row.html
Make sure the downloaded twrp version is located in adb directory as well. Rename it into twrp.img. Then in command prompt type:
fastboot flash recovery twrp.img
(if your device is not recognized check hardware manager for driver. You may use fastboot -i 0x2b4c flash recovery twrp.img instead)
Reboot your phone to system using the following command:
fastboot reboot
That's it. You unlocked bootloader and flashed twrp.
--------------------------------------------------------------------
Hello,
I have done evreything as you described in your "howto"
I have now unlock bootloader and TWRP installed. Each time I try to flash a custom rom I have "fail to mount /vendor (invalid argument)..." error.
Still the custom rom I have tried to flash were recent Pie roms so factory to vendor problem should not be the problem.
I think there is somethig here that I did not understood
Can someone help me please?
Thank you
fastboot does not accept the option -i
Thanks for the detailed description.
weimerd said:
DISCLAIMER:
take care, this will erase all data on phone. I'm not responsible for any data loss. Follow the instructions on your own risk!
---------------------------------------
5. Once in bootloader mode, issue the following command to unlock the device:
fastboot -i 0x2b4c oem unlock-go
└ You’ll see the following output:
...
OKAY [ 0.041s]
finished. total time: 0.041s
--------------------------------------------------------------------
Click to expand...
Click to collapse
I am on step 5 with fastboot oem unlock-go. However, it sas "fastboot: unknown option -i"
What may be the issue?
My phone is zuk z2 pro (z2121)
ZUI 3.5.3165
Android 8.0.0
Android patchdate: 5.02.2018
usb debugging is active
oem unlock is also done
"adb devices" shows me the device. I can also change into bootlaoder using the command "adb reboot bootloader". The phone is connected via
I am stuck and the phone still has the chinese rom, I cannot seem to proceed. Thanks for any pointers.
Hi,
I am in a pickle of my own doing, of course. I followed this video (https://www.youtube.com/watch?v=BT6P5m1XGpw) and now I can only get either the screen that has two Asian languages and English on reboot, or I can get into TWRP.
How do I get it to boot to an OS, any version at this point?
Here are some details:
I have an unlocked boot loader A6013
I was running 9.0.12 and wanted 9.0.13
Using Android File Transfer, I moved Magisk-v18.0.zip, twrp-installer-fajita-3.2.3-2.zip, and OnePlus6TOxygen_34_OTA_020_all_1904032212_38e22c8b9abd42e3.zip into the download folder.
I then rebooted into TWRP recovery, installed twrp-installer-fajita-3.2.3-2.zip
Rebooted to recovery again, and installed OnePlus6TOxygen_34_OTA_020_all_1904032212_38e22c8b9abd42e3.zip
Then I installed twrp-installer-fajita-3.2.3-2.zip again.
Then I rebooted to recovery and tried to install Magisk-v18.0.zip, but found that my directory structure is all mangled with folders named like this "6MTjdFQ0IJuqeJ0kD4vzTB" etc...
I can't find the Download folder anywhere.
Booting normally only gives me the three option of two Asian language options or English. Choosing English gets me the menu to Wipe Data and Cache, Advanced or Exit. Under Advanced I can Reboot to Fastboot, Reboot to recovery or Ver 2.0. Reboot to Recovery send me back to the two Asian languages, etc.
I can boot to TWRP by pressing Vol+ and Power, at which point I have all those options (Install, Wipe, Backup, Restore, Mount, Settings, Advanced, Reboot). I can also see all the "mangled" folders on Android File Transfer, and can sideload things, but dragging and dropping any file into the AFT window is rejected.
Any help would be super appreciated. Please let me know if I didn't give enough information.
Gratefully yours,
Chris El Stupido.
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
This has helped me loads of times ?
i had this problem with my oneplus 6t and i solved it with this solution .. try it maybe it's will work for you insha allah :
1- download tool all for one from this link :
https://forum.xda-developers.com/oneplus-7-pro/development/tool-tool-one-driversunlocktwrpfactory-t3930862
2- open it and put your phone in fastboot or what ever it stuck in it and connect your mobile with your PC .
3- press flash factory image :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4- then press download stock rom
5- it's will take you to fasttboot image page
6- go to oneplus 6t and download the rom
7- then wait its will returns you to fastboot rom and its will work perfectly
then you can download the stock rom again from your stock twrp
Images do not match with the phone! error
jaythenut said:
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
This has helped me loads of times
Click to expand...
Click to collapse
Thanks, I downloaded the 9.0.13, and 9.0.12 versions, I installed the Qualcomm drivers, and see the phone under ports as "Qualcomm" and keep getting the error "Images do not match with the phone!"
All I can do is fastboot mode.
I'm using the stock red OnePlus cable, Windows 10, signature disabled, arghh.
Any tips?
crf1964 said:
Thanks, I downloaded the 9.0.13, and 9.0.12 versions, I installed the Qualcomm drivers, and see the phone under ports as "Qualcomm" and keep getting the error "Images do not match with the phone!"
All I can do is fastboot mode.
I'm using the stock red OnePlus cable, Windows 10, signature disabled, arghh.
Any tips?
Click to expand...
Click to collapse
Ok try this one https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3860279
trying Tool all in one...no luck
jaythenut said:
Ok try this one https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3860279
Click to expand...
Click to collapse
Thanks, I downloaded that Tool All in One app as well as Fastboot and ADB for Windows.
By way of review, by phone only boots to the Fastboot screen showing:
Product Name: sdm845
Variant: SDM UFS
Bootloader Version: [blank]
Baseband Version: [blank]
Serial Numbr: 7faf37cb
Secure Boot: Yes
Device Status: unlocked
In AIO:
- it is not autodetected under Model Auto-Detect
- Under Bootloader, the Bootlaoder Status shows "your bootloader is Unlocked"
- Under Rebooter, I can reboot the phone
- Under REcovery Flasher and Root, when I choose TWP 3.2.3 OP6T, and press Flash I get:
- Booting TWRP...
- Sending "boot.img" (30288kb) . OKAY
- Booting . Failed (remote: "failed to load/authenticate boot image: Load Error')
- fastboot error: Command Failed
- Waiting the TWRP boots...
- * daemon not running; starting now at tcp:5037
- * daemon started successfully
nothing happens after that in the terminal window, or on the phone.
What am I missing ? sigh, many thanks for your help.
crf1964 said:
Thanks, I downloaded that Tool All in One app as well as Fastboot and ADB for Windows.
By way of review, by phone only boots to the Fastboot screen showing:
Product Name: sdm845
Variant: SDM UFS
Bootloader Version: [blank]
Baseband Version: [blank]
Serial Numbr: 7faf37cb
Secure Boot: Yes
Device Status: unlocked
In AIO:
- it is not autodetected under Model Auto-Detect
- Under Bootloader, the Bootlaoder Status shows "your bootloader is Unlocked"
- Under Rebooter, I can reboot the phone
- Under REcovery Flasher and Root, when I choose TWP 3.2.3 OP6T, and press Flash I get:
- Booting TWRP...
- Sending "boot.img" (30288kb) . OKAY
- Booting . Failed (remote: "failed to load/authenticate boot image: Load Error')
- fastboot error: Command Failed
- Waiting the TWRP boots...
- * daemon not running; starting now at tcp:5037
- * daemon started successfully
nothing happens after that in the terminal window, or on the phone.
What am I missing ? sigh, many thanks for your help.
Click to expand...
Click to collapse
Not to sure try and install OS 13 sounds like your phone is completely wiped so install OS get it to boot setup again then try twrp
All Fixed!
jaythenut said:
Not to sure try and install OS 13 sounds like your phone is completely wiped so install OS get it to boot setup again then try twrp
Click to expand...
Click to collapse
I ran this process and came back finally!
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
After 6 hours upgrading from 9.0.12 to 9.0.13 I have learned my lesson. Not sure it was worth a 0.0.01 update. Yikes!
Thanks to all! Your ideas and support were essentil to my sanity and the process.
is there a tool for oneplus 6? or t6.
Anybody else have the gen 2 7" Onn tablet from Walmart and get a recent firmware upgrade (within the past few weeks)?
I have two of these devices. I got them all set up and secured for my two young kids for Christmas presents. Between when I finished configuring them and Christmas morning, some kind of update was pushed out. Now every time I start them up, I get a notice to try to install a firmware upgrade. The kids can't bypass it easily and it has become quite the inconvenience. When I try to complete the update, it fails.
I'm running both the tablets with unlocked bootloaders and rooted with Magisk. I assume this is why the update fails. If it even is a real update. The link in the message goes to an RCA website that doesn't exist. I don't care about the update, but I hate that it tries to install it every time I boot up the tablets. I have disabled "Automatic System Updates" from Developer Options. I have the Google Play store disabling auto-updates as well. I don't want to re-lock the bootloader and have to then unlock it again, and re-install/configure the tablet from scratch again.
Anyone have any ideas on A) how to get the update to work or B) How to ignore the update and get it to stop bothering me? I'm happy to push a new system image if anyone has successfully figured out what can be updated.
Here's what is displayed on the screen and what the update process shows. My guess is the problem lies with the patched boot.img but I'm not ready to wipe it back to stock yet because I'm not good at pulling it back off. Luckily after failing to update I can reboot without trouble. Also I can dismiss this message easily, but my kids can't, and it seems to be unpredictable when it will actually pop up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am having the same issue, but only on one of my two tablets. I haven't been able to figure it out either. I have tried to download it and apply from recovery. I have tried sideloading from ADB. Every time it fails. I haven't figured out how to ignore it either. The only time it seems to pop up is when I first start the tablet. I just use the nav bar to close the update window and go on.
Okiera29 said:
I am having the same issue, but only on one of my two tablets. I haven't been able to figure it out either. I have tried to download it and apply from recovery. I have tried sideloading from ADB. Every time it fails. I haven't figured out how to ignore it either. The only time it seems to pop up is when I first start the tablet. I just use the nav bar to close the update window and go on.
Click to expand...
Click to collapse
From the error messages I get I'm guessing it's a problem with the boot.img as it's patched by Magisk. I can reflash the stock boot.img but then I loose root. If it does update, I don't have root and am not skilled enough to pull the new updated boot.img without root.
If anyone out there has a good tutorial on doing that I'd be happy to try to get the new updated image files to flash.
I'm having a related issue with the same tablet (10015685-E): I got the request to update the firmware, accepted, it appeared to install over the course of ~5 minutes, and after reboot, it is now stuck in an infinite loop in which it boots to the onn logo screen, goes black, and repeats. I assume it's crashing during boot.
I am able to enter recovery mode (see attached pic), but doing a cache wipe and factory reset from the recovery screen did not remedy this sad state of affairs.
I'm happy to load a stock ROM if that would restore functionality, but I don't have one. Any advice welcome. Thanks.
chromoly said:
I'm having a related issue with the same tablet (10015685-E): I got the request to update the firmware, accepted, it appeared to install over the course of ~5 minutes, and after reboot, it is now stuck in an infinite loop in which it boots to the onn logo screen, goes black, and repeats. I assume it's crashing during boot.
I am able to enter recovery mode (see attached pic), but doing a cache wipe and factory reset from the recovery screen did not remedy this sad state of affairs.
I'm happy to load a stock ROM if that would restore functionality, but I don't have one. Any advice welcome. Thanks.
Click to expand...
Click to collapse
Do you have the stock ROM? You can try to just flash the boot.img which isn't altered during a factory reset. It would reverse the update but it appears the update isn't working anyway.
PleaseBeNicetoMe said:
Do you have the stock ROM? You can try to just flash the boot.img which isn't altered during a factory reset. It would reverse the update but it appears the update isn't working anyway.
Click to expand...
Click to collapse
I don't; I'd appreciate a link to the stock ROM or boot.img. Thanks.
chromoly said:
I don't; I'd appreciate a link to the stock ROM or boot.img. Thanks.
Click to expand...
Click to collapse
You can try my files from here
Google Drive: Sign-in
Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).
drive.google.com
PleaseBeNicetoMe said:
You can try my files from here
Google Drive: Sign-in
Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).
drive.google.com
Click to expand...
Click to collapse
Thanks. I got your files and tried a couple of things, neither of which worked:
I tried loading your stock image via ADB, but got "Signature verification failed. Error 21" after loading.
I tried flashing just magisk_patched boot.img via ADB in fastboot mode, but got "Download is not allowed on locked devices".
So perhaps the device has to be unlocked before #2 will work. Any thoughts on #1?
Thanks again.
chromoly said:
Thanks. I got your files and tried a couple of things, neither of which worked:
I tried loading your stock image via ADB, but got "Signature verification failed. Error 21" after loading.
I tried flashing just magisk_patched boot.img via ADB in fastboot mode, but got "Download is not allowed on locked devices".
So perhaps the device has to be unlocked before #2 will work. Any thoughts on #1?
Thanks again.
Click to expand...
Click to collapse
Did you try flashing the boot.img this way with the vbmeta.img first?
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot boot.img
fastboot reboot
For all of those three fastboot commands (vbmeta, cache, boot), I get "not allowed on locked device" errors.
Also, do you have the stock boot.img, vs. "magisk_patched boot.img"?
I appreciate the help.
Code:
$ fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
target reported max download size of 536870912 bytes
sending 'vbmeta' (4 KB)...
FAILED (remote: Download is not allowed on locked devices)
finished. total time: 0.001s
$ fastboot erase cache
erasing 'cache'...
FAILED (remote: Erase is not allowed on locked devices)
finished. total time: 0.000s
$ fastboot flash boot boot.img
error: cannot load 'boot.img': No such file or directory
$ fastboot flash boot ../magisk_patched_boot.img
target reported max download size of 536870912 bytes
sending 'boot' (9152 KB)...
FAILED (remote: Download is not allowed on locked devices)
finished. total time: 0.000s
Ok, here's one. I have the same tablet, not rooted, not modified, just stock. The update fails because it says update.zip isn't found after the download... Anyone have a way to fix? After the error, the whole tablet locks up and I have to force reboot...
chromoly said:
For all of those three fastboot commands (vbmeta, cache, boot), I get "not allowed on locked device" errors.
Also, do you have the stock boot.img, vs. "magisk_patched boot.img"?
I appreciate the help.
Code:
$ fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
target reported max download size of 536870912 bytes
sending 'vbmeta' (4 KB)...
FAILED (remote: Download is not allowed on locked devices)
finished. total time: 0.001s
$ fastboot erase cache
erasing 'cache'...
FAILED (remote: Erase is not allowed on locked devices)
finished. total time: 0.000s
$ fastboot flash boot boot.img
error: cannot load 'boot.img': No such file or directory
$ fastboot flash boot ../magisk_patched_boot.img
target reported max download size of 536870912 bytes
sending 'boot' (9152 KB)...
FAILED (remote: Download is not allowed on locked devices)
finished. total time: 0.000s
Click to expand...
Click to collapse
The stock boot.img should be in the STOCK ROM .zip file in my GDrive folder above. I reuploaded it just in case.
My guess is the bootloader is locked. Did you unlock it before? Try running
fastboot flashing unlock
Follow the prompts. If that worked then try flashing vbmeta and the other steps from above. That's my only idea right now.
chromoly said:
For all of those three fastboot commands (vbmeta, cache, boot), I get "not allowed on locked device" errors.
Also, do you have the stock boot.img, vs. "magisk_patched boot.img"?
Click to expand...
Click to collapse
If you did not unlock your bootloader before all this happened, then I believe you will not be able to flash via fastboot commands. You can try to use the SP Flash Tool to install the earlier stock ROM. If you look through my thread from earlier, you will find a full dump of the original pre-update ROM
Try this post... Hang on, that was for the A variant. Look for a post by Fred, he dumped the entire ROM with scatter file(needed for SP tools to function properly) You may still need my super.img referenced below
Do not use the one from Tytydraco as it is for the A variant of the tablet and will cause some screwy issues(personal experience on my E variant) If you are looking for the super.img you can use the one I pulled from my tablet.
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
Okiera29 said:
I am having the same issue, but only on one of my two tablets. I haven't been able to figure it out either. I have tried to download it and apply from recovery. I have tried sideloading from ADB. Every time it fails. I haven't figured out how to ignore it either. The only time it seems to pop up is when I first start the tablet. I just use the nav bar to close the update window and go on.
Click to expand...
Click to collapse
We're you ever able to find a work around? I may have fixed it, at least this works for me because I don't care about the update ever. I don't know your level of expertise with these. I'm definitiely just proficient enough to be dangerous. I can give more details than this if you need it.
You'll need a rooted tablet with Magisk and the Terminal Debloater (Terminal Emulator) module installed.
Start your Terminal Emulator app (I use Termux), type su (grant superuser if you haven't already) and start the Debloater by typing "debloat"
From the menu I choose 1 - System Apps and for me on the second menu #13 is Firmware Update
Choose that to uninstall, restart the tablet, and the popup error is gone!
This works for me for my 7" version. I have a 10" version too that doesn't have the same app, but it's called Wireless Update, and I uninstalled that using the same process successfully.
It's a great way to ge tall those pesky Walmart apps off too, PLUS I disabled the extra Walmart nav button (It didn't disappear but nothing happens when tapped, so it's one less thing to help my kids escape from when they get stuck in it).
Hope this helps a bit.
PleaseBeNicetoMe said:
We're you ever able to find a work around? I may have fixed it, at least this works for me because I don't care about the update ever. I don't know your level of expertise with these. I'm definitiely just proficient enough to be dangerous. I can give more details than this if you need it.
You'll need a rooted tablet with Magisk and the Terminal Debloater (Terminal Emulator) module installed.
Start your Terminal Emulator app (I use Termux), type su (grant superuser if you haven't already) and start the Debloater by typing "debloat"
From the menu I choose 1 - System Apps and for me on the second menu #13 is Firmware Update
Choose that to uninstall, restart the tablet, and the popup error is gone!
This works for me for my 7" version. I have a 10" version too that doesn't have the same app, but it's called Wireless Update, and I uninstalled that using the same process successfully.
It's a great way to ge tall those pesky Walmart apps off too, PLUS I disabled the extra Walmart nav button (It didn't disappear but nothing happens when tapped, so it's one less thing to help my kids escape from when they get stuck in it).
Hope this helps a bit.
Click to expand...
Click to collapse
Worked like a champ on both tablets. I only use them for reading, light gaming and watching youtube in bed. So like you, the updates are not imperative for me.