Related
Hello everyone,
I have an OG Pixel 5'', the stock Android was 7.1.2 and I updated it to Android 8.1 Oreo. Bootloader is unlocked, and I am able to install a TWRP 3.2.1-0 no problems. Phone at the time worked well. Now I have tried to flash an ElementalX Kernel on my device. This worked and I managed to boot. However, a message "There is an internal problem with your device, please contact the manufacturer". There is a thread to fix this and I should have done my research better.
Anyway, I went into TWRP and did a complete wipe of the phone, thinking that I could have just boot into TWRP again and copy the stock flashable zips to reflash the ROM.
It turns out that:
a) TWRP doesnt work. I.e when I got into fastboot mode (Power + Volume Down) and selected Recovery, the phone flashed to screen with Google image and then flashed back into the one with the green Android.
b) I managed to boot twrp via fastboot from my computer. So I booted into fastboot mode, and then on my computer, did: fastboot boot <twrp3.2.1.zip>. This worked and I managed to get into TWRP again. However, I cannot transfer file to flash. I.e when the phone showed up on my computer in TWRP, I cannot drag and drop anything into mounted folder.
I have tried the following to get stock ROM from this website: https://developers.google.com/android/images
a) I decided to look at ADB Sideload. So from the above website, I downloaded the zip files under Full OTA Images and then in TWRP, I went into Advance and chose ADB SIdeload. On my computer, I did "adb sideload name_of_zip_file_downloaded". The process started but ended very quickly, the finished time was 0.00 second, which means that nothing happened. Clearly, TWRP console showed that it is unable to mount /data and other folders. I guess the reason is that I am running a "live" TWRP? I checked by going back to TWRP mainscreen and tried to mount. However, all hard drives show 0MB (OTA USB and the main drive).
b) I used factory images approach by downloading zip from the same website, but this time under Factory Images. For this one, I unzip the files to a separate folder. Then I did flash-all.sh script but it said that my fastboot is too old.
So... to fix fastboot, I tried: (I am on Ubuntu 16.04.02)
a) Remove whole android fastboot with sudo apt-get remove, then reinstalled => Did not work. Still fastboot is too old
b) Download entire Android SDK from here: https://developer.android.com/studio/install.html. Fastboot still didnt work
c) From the Android Studio website, I tried to download just the command line tools. However, I could not find the folder with fastboot in it. A Google search shows that the fastboot and adb should be in platform-tools folder. Couldnt find any
Once again, I apologize for a very very long thread (It's 5am and I am trying to figure this thing out). Please, let me know if you guys can offer any help. Any help is greatly appreciated. FYI, I am coming from a Moto Z Play, and if things happen I would just boot into TWRP and copy the zip over. Clearly, this is not the case. This is my 1st Pixel as well.
Please let me know and thank you very very much.
Installing ex messes with the boot.IMG you need to reflash twrp after. Also don't manually flash stock zips that doesn't even make any sense. Download the latest android sdk or base platform tools then get the latest factory image and extract it into platform tools. Then go into fastboot and manually flash the official factory image
To use fastboot on ubuntu you have to put sudo infront of the command: sudo fastboot ........, Because of a permissions thing.
Sent from my Google Pixel using XDA Labs
Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel
maxwell0312 said:
Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel
Click to expand...
Click to collapse
I personally recommend using a custom kernel just make sure to follow the OP exactly. As the kernel and twrp are usually stored in the boot.img together and the kernel overwrites the boot.img the problem was likely that you just did things in the wrong order which would cause twrp to be removed. Typically the order of installing custom stuff from stock goes this way: flash_all to restore stock boot.img, boot twrp, factory wipe, flash rom, flash twrp, boot rom, reboot into recovery, flash kernel, flash twrp, reboot system, reboot recovery, flash magisk. Some rooms vary as they may require you to do things like flash a vendor img or delete the vendor overlay folder(always follow OP).
Phone: OnePlus 7 Pro
Build number: Oxygen OS 10.0.3 GM21BA
Anndroid Version: 10
Model: GM1913
Hi all,
I received yesterday my Oneplus 7 Pro. My objective is to install nethunter fully rooted.
After looking the requirements in the offensive security website i noticed i need 3 things
TWRP
Magisk
DM-Verify
I started with TWRP watching different tutorials and comparing them but they are similar.
- Installed sdk platform tools and Minimal adb/fastboot ( tried both ways )
-unlocked the bootloader and enabled usb debug mode.
- Once i do " fastboot boot twrp.img " everything seems " okay " in the terminal, but the phone becomes stuck in fastboot mode logo image, it never actually boots into the twrp.
In a different tutorial, i replaced the "fastboot boot twrp.img" with " fastboot flash boot twrp.img ". This broke my phone i couldn't start the android or go the recovery mode, i couldn't leave fastboot mode unless to restart or to turn off the phone. I fixed this by " fastboot flash boot boot.img " that i had available in the platform tools folder.
I tried different twrp images:
TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Pie by mauronofrio
twrp-3.3.1-4-guacamole.img
Nothing seems to work, i don't know what else to try or what am i doing wrong.
I've been 8 hours around this so any help would be deeply appreciated.
Kind regards,
C666PO said:
Phone: OnePlus 7 Pro
Build number: Oxygen OS 10.0.3 GM21BA
Anndroid Version: 10
Model: GM1913
Hi all,
I received yesterday my Oneplus 7 Pro. My objective is to install nethunter fully rooted.
After looking the requirements in the offensive security website i noticed i need 3 things
TWRP
Magisk
DM-Verify
I started with TWRP watching different tutorials and comparing them but they are similar.
- Installed sdk platform tools and Minimal adb/fastboot ( tried both ways )
-unlocked the bootloader and enabled usb debug mode.
- Once i do " fastboot boot twrp.img " everything seems " okay " in the terminal, but the phone becomes stuck in fastboot mode logo image, it never actually boots into the twrp.
In a different tutorial, i replaced the "fastboot boot twrp.img" with " fastboot flash boot twrp.img ". This broke my phone i couldn't start the android or go the recovery mode, i couldn't leave fastboot mode unless to restart or to turn off the phone. I fixed this by " fastboot flash boot boot.img " that i had available in the platform tools folder.
I tried different twrp images:
TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Pie by mauronofrio
twrp-3.3.1-4-guacamole.img
Nothing seems to work, i don't know what else to try or what am i doing wrong.
I've been 8 hours around this so any help would be deeply appreciated.
Kind regards,
Click to expand...
Click to collapse
I have an almost identical problem to you.
except: my device is GM1910, I had a stock hydrogen OS, which has been converted to oxygen OS.
so far, I have tried twrp-3.3.1-0, 3.3.1-2, 3.3.1-3, 3.3.1-4, on oxygen OS version 10.0.2.GM21AA, 10.0.3.GM21AA, and 10.3.0.GM21AA, all would stuck at the fastboot mode logo screen
Rolling back to a lower version of oxygen OS, including version 9.5.1 and 9.5.7 causes my OP7P in bootloader mode no longer recognized by "fastboot devices", or even by "dmseg" as a usb device.
I received a suggestion of trying the latest TWRP 3.3.1-74 build, which I intend to try later tonight, but got not so optimistic about, seeing that you've experimented with TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
One observation I do like to make, is that android 9 is considered as Pie while android 10 was developed from android Q.
since your device is already android 10 at version 10.0.3, should you still use the Pie TWRP build?
OblixioN said:
One observation I do like to make, is that android 9 is considered as Pie while android 10 was developed from android Q.
since your device is already android 10 at version 10.0.3, should you still use the Pie TWRP build?
Click to expand...
Click to collapse
Hi OblixioN,
I tried the image with the Q at the end: TWRP 3.3.1-74 Unified Unofficial Q by mauronofrio and it worked. I had no idea what the Q or Pie meant so your information just solved my problem. I assume it will work for you.
Huge thanks!
Thanks - worked for me as well!
Unfortunately I formated before getting to this solution, so rather unnecessary for me, but what I did was getting the unofficial twrp for guacamole here:
h-t-t-p-s://androidfilehost.com/?fid=4349826312261707787
(from this post: https://forum.xda-developers.com/oneplus-7-pro/development/recovery-unofficial-twrp-recovery-t3931322)
Then I booted to fastboot at ran
Code:
fastboot set_active a
fastboot boot .\twrp-3.3.1-75-guacamole-unified-Q-mauronofrio.img
fastboot set_active b
fastboot boot .\twrp-3.3.1-75-guacamole-unified-Q-mauronofrio.img
Now I could boot into twrp, it found all the internal data storage, and I could sideload
Code:
adb sideload .\twrp-installer-3.3.1-4-guacamole.zip
adb sideload .\Magisk-v20.3.zip
C666PO said:
I had no idea what the Q or Pie meant so your information just solved my problem.
Click to expand...
Click to collapse
It means if you are on Android Q, you need to use the TWRP version that supports Android Q.
Hey, I seem to have the same problem but how do u get it unstuck from the Fastboot Mode so I can try another version of TWRP?
OrionGiant said:
Hey, I seem to have the same problem but how do u get it unstuck from the Fastboot Mode so I can try another version of TWRP?
Click to expand...
Click to collapse
hey there.
So, first of, You restart it by pressing and holding volume up, down and power at the same time for 10+ seconds.
And second, try updating Oxygen OS to its latest version. It works for me now, just unpacked a new OnePlus 7 Pro, didn't work on Android 9, works on Android 10 latest update.
OrionGiant said:
Hey, I seem to have the same problem but how do u get it unstuck from the Fastboot Mode so I can try another version of TWRP?
Click to expand...
Click to collapse
While in fastboot , " fastboot boot twrp.img
Hi!
I'm on the latest official OxygenOS 11 and am having the exact same issue you hade above.
Tried everything mentioned above and the phone is still boot looping :'(
Any more tips?
SABMAN said:
Hi!
I'm on the latest official OxygenOS 11 and am having the exact same issue you hade above.
Tried everything mentioned above and the phone is still boot looping :'(
Any more tips?
Click to expand...
Click to collapse
I tried installing a new kernal and after that mine would go directly to bootloader, no matter what I did it went directly to bootload, thankfully fastboot was still active but using boot cmd into anything would fail,, ,I started my msm tool, and rebooted into edl and as soon as a com port became active on the MSM panel I hit start, and it took off running and did it's thing,
I think my issue had two reasons!
1. The boot.img file i used was from the earlier Oxygen update not the version i had just installed.
2. The phone encryption (but i doubt this!)
Anyway since nothing helped i erased the phone and restored it Now it's working again!
Motorola Moto G7 Play
Codename: CHANNEL
Boost Mobile Variant
Model No. XT1952-4
OBSOLETE THREAD
IMPORTANT NOTE:
At the time this thread was created, Motorola Mobility had not yet released the official stock Android 10 update for this variant of the CHANNEL. Because this variant has long since received the official Android 10 update, this thread is beneficial only for experimental or educational purposes. While you may certainly install RETAIL Android 10 firmware on the Sprint compatible xt1952-4, it is recommended always to install the latest official Android 10 firmware package released exclusively for this variant. Official Motorola stock firmware packages are available for the Boost Mobile/Sprint variant here https://mirrors.lolinet.com/firmware/motorola/channel/official/Sprint/
COMPATIBILITY:
Although this guide specifies the Boost Mobile (xt1952-4) variant of the CHANNEL, device owners have tested and confirmed that this Android 10 firmware is compatible with other variants/models. Namely, the MetroPCS xt1952-6 and the T-Mobile xt1952-T are confirmed. It is safe to assume that, because this is a RETAIL based official firmware build, compatibility should be universal for all region based retail models.
DISCLAIMER:
By proceeding further, you are assuming full responsibility for the operability and integrity of your device. Although this is an official firmware package, installation of firmware has an inherent risk of damaging your device or otherwise rendering it inoperable if the instructions are not followed carefully. Follow this detailed guide carefully and concisely and the installation should go smoothly. However, I am absolved of any liability in the event you break something. If you do mess something up, either myself or one of the many knowledgeable members herein will try to assist you.
OFFICIAL ANDROID 10:
For owners of the Moto G7 Play, it's no secret that the official Android 10 OTA update has already began rolling out to device owners in Brazil. As such, it probably will not be long before device owners in the US begin seeing a notification for the Android 10 update. In the meantime, for owners of the Boost Mobile variant (xt1952-4) who want to manually update to Android 10 by flashing the official Android 10 retail firmware package, I have put this simple guide together to assist you. In essence, to update manually, you will need to install the Android 10 firmware package via fastboot or RSD-Lite. This guide is premised upon the fastboot mode method. This Android 10 firmware is stable and may be used for your daily driver ROM. Look to the end of this guide for reported bugs.
BUILD INFO:
Android Version: Android 10
Build Region: RETAIL
Build No. QPY30.52-22
Kernel Version: 4.9.206-perf+
Radio Version: M632_41.178.01.156R
FSG Version: FSG-8953-25.163
Bootloader Version:2.1-channel_retail-315bc626c6-200423
System Version: 30.1.24.channel.retail.en.US
Build Date: April 13, 2020
Security Patch Level: April 1, 2020
ANDROID 10 UPDATE FEATURES:
• Optimized Fast Charging
• Bug Fixes for Battery Drain Issues
• Power Optimizations
• System-Wide Dark Theme
• Gesture-Based Navigation
• Privacy & Location Controls
• Sound Effects -- Stock Equalizer & Amplifier
• Smart Reply w/Messaging Apps
• Incognito Mode w/Google Maps
• Focus Mode
• Live Caption
• New Parental Controls
• New Moto Actions
INSTALLATION:
For those members who are not familiar with installing official firmware via fastboot mode, I will outline the exact steps below, including links to the files you'll need for the job. This guide requires a Windows PC or laptop, running Windows 7, 8.1 or 10 (32 or 64-bit). While fastboot can be used with other operating systems, this guide is outlined for Windows based systems only:
1. First, on your Windows PC or laptop, you will need to download and install the latest version of Motorola Device Manager, to ensure installation of up-to-date USB device drivers. Motorola Device Manager can be downloaded here: https://support.motorola.com/us/en/solution/MS88481
2. Next, download and install the latest fastboot and ADB utilities for flashing the firmware to your device. We will be using the Minimal ADB & Fastboot tools, version 1.4.3. On your PC or laptop, visit this link https://mega.nz/file/dVR3xCJL#GjcIXtNcCoB7R9DJtyqJ3dfOmeuGuPUvx6FKgp23yrc
3. Now download the official Android 10 retail firmware package from the Downloads section below;
4. Extract the contents of the firmware package zip you just downloaded to your Minimal ADB & Fastboot directory;
5. Boot your Moto G7 Play into AP Fastboot mode. With the device powered off, hold the power button along with the volume down button for around 8 seconds or until AP Fastboot mode appears on your device display;
6. Connect your device to your PC or laptop using the OEM supplied -- or quality equivalent -- USB to USB type C charging/syncing cable;
7. Open a command prompt in the path of your Minimal ADB & Fastboot directory. Execute the following command: fastboot devices
If your PC/laptop & device are properly synced, the command window will return an alphanumeric string synonymous with your device serial number. If you are not properly synced, try another USB syncing cable, change USB ports on your computer, or try reinstalling the USB device drivers.
**NOTES: by following these installation instructions, you will wipe your device of all userdata. Before proceeding further, make a backup of any important files and media.
Once you have confirmed proper syncing between your device and PC/laptop, execute the following fastboot commands, preferably in this order:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash logo logo.bin
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fb oem config fsg-id boost
fb oem config carrier boost
fastboot erase DDR
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Upon reboot, your Boost Mobile Moto G7 Play will be running stock Android 10. During setup, select the "Use Mobile Data" option instead of using WiFi. This will allow your device to establish its initial 4G/LTE data connection on the Boost Mobile network. Once setup is complete, your cellular data, voice and messaging services should be functioning normally. Make a test phone call and send a test text message to confirm.
DOWNLOADS:
Android 10 Retail Firmware:
•Build No. QPY30.52-22 (April 1 SPL): https://mega.nz/file/YIZnwAAZ#17HH-vbEsbxQVPNLjvgNqdTHFI4Ow2ah6SNC4Nnw9ec
•Build No. QPYS30.52-22-2 (June 1 SPL): https://mega.nz/file/lB5gkaqK#BD-r7dSTw8dgZAfI90pJq7LB_XJvqcvSVshXbLo-yic
Android 9 Pie Stock Firmware:
• Official Firmware Builds: https://mirrors.lolinet.com/firmware/moto/channel/official/Sprint/
BUGS:
• PRL/Domestic Roaming:
When roaming outside of the home network, the device may give a mobile IP registration response error (MIP Error 67-- Mobile Node Failed Authentication), and the cellular signal may become unstable. This is most likely due to the lack of an integrated PRL (Preferred Roaming List) provisioning service within the retail firmware. I am looking for a workaround: possibly implementing the Boost Mobile radio firmware from Android 9, or including the SprintDM mobile provisioning service as an add-on;
• Gesture/Navigation Features:
As XDA Member @JohnSmith8786 has pointed out, some of the native Gesture Navigation features in the RETAIL Android 10 firmware are somewhat unstable and buggy at times. This bug has been reported to Motorola Mobility via official bug report. Since this issue does not appear to be specific to a particular variant/model, and has been reported on various different models, this issue is likely unique to the RETAIL Android 10 firmware builds, and will likely be resolved by stability improvements/bug fixes in a future OTA(s).
Please report any bugs or instabilities in comments below. Also, please provide confirmation regarding compatibility of this Android 10 firmware on specific Moto G7 Play models. In theory, this firmware should work on any model with an unlocked bootloader. As all Android enthusiasts, modders and devs know, confirmation is always better than theory.
Could it work on XT1952-6 from MetroPCS?
mickem said:
Could it work on XT1952-6 from MetroPCS?
Click to expand...
Click to collapse
Can confirm working on XT1952-6 & XT1952-T
I tested stock AndroidQ for XT1952-2 ATTMX QPYS30.52-22-2 from lollinet mirrors on MPCS XT1952-6 and flashed with RSDLite. Until now everything works fine. Still testing.
mickem said:
I tested stock AndroidQ for XT1952-2 ATTMX QPYS30.52-22-2 from lollinet mirrors on MPCS XT1952-6 and flashed with RSDLite. Until now everything works fine. Still testing.
Click to expand...
Click to collapse
I used RETAIL, only issue is the baked in gesture navigation gets squirrely sometimes
JohnSmith8786 said:
Can confirm working on XT1952-6 & XT1952-T
Click to expand...
Click to collapse
Thank you very much. I will add that to my OP heading. Yeah I've noticed some slight buggy behavior on the RETAIL Android 10 gesture navigation features too. Motorola Mobility has been notified of this issue, so perhaps a future OTA will fix this.
So this shouldn’t affect my modem or data connection on the Sprint Nationwide Network for Boost?
GRiZZ91 said:
So this shouldn’t affect my modem or data connection on the Sprint Nationwide Network for Boost?
Click to expand...
Click to collapse
Correct. Flashing this firmware to a device active on the Boost Mobile network will continue to function normally. I have noticed some buggy behavior when roaming outside of the home network. Other than that, your device should function just as if you were using the Sprint firmware build.
Sorry I was rusty
Does anyone know if in this Android version call recording goes back to our Motorola? On Android 9 I had to root phone for enable call recording. How is it now?
For those with the Sprint/Boost Mobile variant of the xt1952-4, the latest OTA is live, bringing the Build No. to QPYS30.85-18-6 and the security patch level to October 1. For anybody needing it, I will try to post a link for the entire firmware package this weekend. Here is a link to the latest full firmware package for the Sprint/Boost Mobile xt1952-4 https://mega.nz/file/SmAEwRZL#M4KP8hHHEtBw5fOtHGRuGfDV8F0SUkFENVGctzJagFw
Viva La Android said:
For those with the Sprint/Boost Mobile variant of the xt1952-4, the latest OTA is live, bringing the Build No. to QPYS30.85-18-6 and the security patch level to October 1.
Click to expand...
Click to collapse
Were you able to get Magisk running and the device rooted?
I had the Lenovo rescue tool unbrick my phone and it 30.85-18-11 and I can't get Magisk to stay on, let alone get it rooted.
veryspecialagent said:
Were you able to get Magisk running and the device rooted?
I had the Lenovo rescue tool unbrick my phone and it 30.85-18-11 and I can't get Magisk to stay on, let alone get it rooted.
Click to expand...
Click to collapse
I have a patched boot.image that will root your device.
Viva La Android said:
Ill have a patched boot.image that will root your device.
Click to expand...
Click to collapse
Correction I mean a patched recovery image
Viva La Android said:
You can I stall it via TWRP or fastboot
Click to expand...
Click to collapse
Let me make sure I am not misunderstanding. You want to run official stock Android 10 and root with Magisk, correct? If so, you can certainly do that, but since the Moto G7 Play does not have a boot-ramdisk, you ate forced to jump through some hoops to get Magisk installed. You are much better off flashing.offiicial Lineage OS 18.1 (Android 11) and installing Magisk using the typical boot image patching method -- the normal method. LineageOS 18.1 has a boot-ramdisk. If you do not like LineageOS, there are many official Android 11 based custom ROMs available for the CHANNEL. And a few Android 12 custom ROMs. They all include boot-ramdisk.
Viva La Android said:
Let me make sure I am not misunderstanding. You want to run official stock Android 10 and root with Magisk, correct? If so, you can certainly do that, but since the Moto G7 Play does not have a boot-ramdisk, you ate forced to jump through some hoops to get Magisk installed. You are much better off flashing.offiicial Lineage OS 18.1 (Android 11) and installing Magisk using the typical boot image patching method -- the normal method. LineageOS 18.1 has a boot-ramdisk. If you do not like LineageOS, there are many official Android 11 based custom ROMs available for the CHANNEL. And a few Android 12 custom ROMs. They all include boot-ramdisk
Click to expand...
Click to collapse
I've never bothered with custom ROMs. My interests with rooted phones are for practicing forensics and pentesting.
I'm downloading the latest Lineage and will try it that way. I'll report back when completed or I run into issues.
veryspecialagent said:
I've never bothered with custom ROMs. My interests with rooted phones are for practicing forensics and pentesting.
I'm downloading the latest Lineage and will try it that way. I'll report back when completed or I run into issues.
Click to expand...
Click to collapse
Cool. Yeah let me know. Follow the install instructions for LOS 18.1 directly from the Lineage WiKi. The install is not standard TWRP like most Lineage builds. This has to be done using.adb sideload in TWRP mode with a PC.
That should have posted 2 hours ago.
This is what I f'ing loathe about this process because it happens virtually EVERY time regardless of the device or OS or mod that I'm doing.
The first thing I did was make sure sdk tools were updated. There were updates for Android 6 and 10, as well as two new modules to install. It took about a half hour to go through them all, but everything is updated.
Downloaded LoS, latest version, and the recovery image.
Go to the first step on the LoS install, which is to sideload a specific zip file. kay...
-reboot into bootloader, then from there to recovery
-adb sideload <the file>
-on computer: error:closed
-on phone: Error 21, footer is wrong
This nearly ALWAYS happens, and I have yet to find a fix. I google for an answer, keeping results to just within the last year, and someone on Reddit had suggested a fix that worked for the poster. His problem was that he was in stock recovery. He needed to be in LoS recovery.
I think "well, they give you a recovery image separate with the OS download, maybe it's to boot with, like TWRP." So I boot into the bootloader and try to fastboot boot <lineage recovery.img>..........and it just starts up normal. I go to settings and check the build, and it's still the Android 10 version I started with. Tried it again, same results.
So then I get the bright idea to stay where I'm at in stock OS and adb reboot <lineage recovery.img>
Now, on my phone it's in a weird Android Recovery screen. "Can't load Android system. Your data may be corrupted. If you continue to get this message...." Then it gives me two options: Try again or factory reset.
Well, my mama didn't raise no quitter, so I hit Try Again. It goes to the black screen with "N/A" on it (which is what it would do back when I had this thing rooted and everything was peachy until I forgot the lock screen pattern), but then I get that error message again.
I'm going to factory reset and see what happens. Anyone with a solution, feel free to chime in anytime.
Factory reset complete. Now I'm.....still in Android 10, build QPYS30.85-18-11.
Lol, just to clarify where we're at: The process I'd "be much better doing" took three hours to implement just half of the first step, and it led to me having to factory reset because it wouldn't boot.
Hello community,
I kind of ruined my phone into this CrashDump Mode state. Which prevents me from using my phone at all. I'm pretty sure it is 'bricked.
I hope someone could give me some guidance to fix my phone again.
What do I want:
I wish to have the original OxygenOS back on my phone (stock).
What caused the problem:
My goal was to root my phone by unlocking the bootloader, installing Magisk and flashing the ROM from Magisk. Unfortunately, after doing all of this successfully there were some issues. One of them being slow restarts. It could take up to 20 minutes for the phone to start. Other than that it made the phone quite unusable as the media sound didn't work neither did the wifi and microphone. Making me unable to listen to anything but also couldn't make calls. For that reason I decided to unroot the phone again. I used the in-app Magisk full uninstall button to do so. After doing this, the phone didn't boot anymore. It was stuck at the boot loader unlock warning screen. So I figured I had to flash my latest version of OxygenOS on the phone. I grabbed a guide to do this manually on the XDA forums. However, this was a guide for Android 10 I believe. So it didn't seem to flash all the image files I saw listed after doing the payload extractor. This resulted in my phone booting up to the CrashDump Mode. As there were no guides for the version 11.0.5.1, I decided to use a tool listed here on the forums: https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/ However, this is only for version 10 instead of 11. This also didn't seem to work.
Steps done:
Unlocked bootloader:
- Basically by just using: "fastboot oem unlock"
This went successfully.
Rooted the phone:
- Installed Magisk and my boot.img on my phone.
- Created an .img with Magisk.
- Ported the created .img to my pc.
- rooted the phone with fastboot by flashing the .img on my phone for boot_a and boot_b
This went successfully, the phone was rooted.
Unrooting and stock recovery:
- Used the uninstall button within the Magisk app on the phone.
- Tried to manually flash the OxygenOS version 11.0.5.1 on my phone. Note: only a few images were then as they were the only ones listed in a guide.
- Tried the tool listed above.
This all failed.
Phone details:
OnePlus 7 Pro - European - Last version used: 11.0.5.1
Index of /list/Unbrick_Tools/OnePlus_7_Pro/EU_GM21BA/R
Juuuul said:
Hello community,
I kind of ruined my phone into this CrashDump Mode state. Which prevents me from using my phone at all. I'm pretty sure it is 'bricked.
I hope someone could give me some guidance to fix my phone again.
What do I want:
I wish to have the original OxygenOS back on my phone (stock).
What caused the problem:
My goal was to root my phone by unlocking the bootloader, installing Magisk and flashing the ROM from Magisk. Unfortunately, after doing all of this successfully there were some issues. One of them being slow restarts. It could take up to 20 minutes for the phone to start. Other than that it made the phone quite unusable as the media sound didn't work neither did the wifi and microphone. Making me unable to listen to anything but also couldn't make calls. For that reason I decided to unroot the phone again. I used the in-app Magisk full uninstall button to do so. After doing this, the phone didn't boot anymore. It was stuck at the boot loader unlock warning screen. So I figured I had to flash my latest version of OxygenOS on the phone. I grabbed a guide to do this manually on the XDA forums. However, this was a guide for Android 10 I believe. So it didn't seem to flash all the image files I saw listed after doing the payload extractor. This resulted in my phone booting up to the CrashDump Mode. As there were no guides for the version 11.0.5.1, I decided to use a tool listed here on the forums: https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/ However, this is only for version 10 instead of 11. This also didn't seem to work.
Steps done:
Unlocked bootloader:
- Basically by just using: "fastboot oem unlock"
This went successfully.
Rooted the phone:
- Installed Magisk and my boot.img on my phone.
- Created an .img with Magisk.
- Ported the created .img to my pc.
- rooted the phone with fastboot by flashing the .img on my phone for boot_a and boot_b
This went successfully, the phone was rooted.
Unrooting and stock recovery:
- Used the uninstall button within the Magisk app on the phone.
- Tried to manually flash the OxygenOS version 11.0.5.1 on my phone. Note: only a few images were then as they were the only ones listed in a guide.
- Tried the tool listed above.
This all failed.
Phone details:
OnePlus 7 Pro - European - Last version used: 11.0.5.1
Index of /list/Unbrick_Tools/OnePlus_7_Pro/EU_GM21BA/R
Click to expand...
Click to collapse
This is how I go back to stock
You can use MSM tool to revert OOS, or you can try this step:
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage or otg drive. Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots
In your case skip to number 2 and after booting to TWRP then format data then install twrp
hammered58 said:
This is how I go back to stock
You can use MSM tool to revert OOS, or you can try this step:
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage or otg drive. Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots
In your case skip to number 2 and after booting to TWRP then format data then install twrp
Click to expand...
Click to collapse
Hey,
Thanks for your reply! I currently don’t have twrp on my phone but I could look at it. Do you have a link for MSM tool as download and possibly a guide?
Juuuul said:
Hey,
Thanks for your reply! I currently don’t have twrp on my phone but I could look at it. Do you have a link for MSM tool as download and possibly a guide?
Click to expand...
Click to collapse
You actually boot into TWRP it does not have to be installed,, you install it once you boot into it plus you would probably need a otg because you do not have a OS . Here's a link to the Msm tools
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7_Pro/Global_GM21AA/
There are several great write ups on how to use and install msm tool right here in the op7p forum I will see what I can find and post later
[OP7PRO][LATEST OOS 11.0.5.1 GM21AA/GM21BA] Collection of unbrick tools
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
Hello everyone, I'm porting LineageOS to Xiaomi 12, but I haven't unlocked the bootloader.
Can someone help me testing my port? I'll be appreciated if you could help me.
Requirements:
A Xiaomi 12 with unlocked bootloader.
Have enough time to test.
Know how to use logcat.
Speak English or Chinese.
Please contact me at Link deleted or Link deleted if you are willing to help. Thank you very much.
If you have a Deleted, just add my account ID Accound deleted please.
Edit moderation - Unauthorized links - Sib64 - moderator
awsome！kuan brother niubi！
Hey, i still have to wait some 120-ish hours to get my bootloader unlocked, but once I do, I can give it a try
fygesser said:
Hey, i still have to wait some 120-ish hours to get my bootloader unlocked, but once I do, I can give it a try
Click to expand...
Click to collapse
could test the ROM?
Hi, do I need to build it from source, or do you provide the binary?
do you provide the binary?
Is there a QQ group for this?
I compiled a rom from this device tree. But I don't know what's wrong. Boot into recovery mode only once.Then keep looping into fastboot.
NothingToHere said:
I compiled a rom from this device tree. But I don't know what's wrong. Boot into recovery mode only once.Then keep looping into fastboot.
Click to expand...
Click to collapse
how to compile bro
Are there any tutorial on how to compile a rom from device tree?
roesip said:
Are there any tutorial on how to compile a rom from device tree?
Click to expand...
Click to collapse
Find a phone you like from the lineageos official support list, where there is a detailed compilation process
Using already LOS!
ydd0ras said:
Using already LOS!
Click to expand...
Click to collapse
On Xiaomi 12? Which Build from which source?
Check here
Release LineageOS 19.1 for Xiaomi 2201123G (cupid) · arian-ota/ota
📅 Build date: 2022-06-19 🛡️ Security patch: 2022-06-05 💬 Variant: VANILLA 🗒️ Changelog SHA-256 checksum 4b31804abcd9fc54afb8b89ec2ed2bde3aab49e78065b31bd02321281677c161
github.com
ydd0ras said:
Check here
Release LineageOS 19.1 for Xiaomi 2201123G (cupid) · arian-ota/ota
📅 Build date: 2022-06-19 🛡️ Security patch: 2022-06-05 💬 Variant: VANILLA 🗒️ Changelog SHA-256 checksum 4b31804abcd9fc54afb8b89ec2ed2bde3aab49e78065b31bd02321281677c161
github.com
Click to expand...
Click to collapse
I, i Will be pleased if you upload a flashing guide.
Therazorsedge said:
I, i Will be pleased if you upload a flashing guide.
Click to expand...
Click to collapse
OK, I have wrote a flashing guide for Windows users, tho I don't use Windows so I hope all steps are correct:
Flashing LOS on Cupid
Xiaomi 12 LOS ROM flashing
Prerequisites:
Your bootloader must be unlocked.
You should use latest platform tools on Windows. https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Your device should be charged above 50%. Well, it doesn't have to be, but this is just for your phones safety.
Download all required files - ROM, boot, vendor_boot, dtbo and recovery.
Make a proper backup if needed and push it to another storage.
First steps:
After you have unlocked the bootloader, device will reboot automatically. Finish the setup, enable developer settings and finally enable USB-Debugging in developer settings.
In Windows open the folder in which you have unzipped the platform tools.
Hold left shift and press right click
click "open powershell window here"
Type in Terminal for example "adb devices" and grant the permissions for this PC on your device.
Reboot your device to fastboot and connect it with your PC.
The flashing procedure:
Flash boot, vendor_boot, dtbo and recovery:
Type in Windows Terminal:
fastboot flash boot lineage-19.1-20220617-UNOFFICIAL-cupid-boot.img
fastboot flash vendor_boot lineage-19.1-20220617-UNOFFICIAL-cupid-vendor_boot.img
fastboot flash dtbo_ab lineage-19.1-20220617-UNOFFICIAL-cupid-dtbo.img
fastboot flash recovery lineage-19.1-20220617-UNOFFICIAL-cupid-recovery.img
and finally
fastboot reboot recovery or
reboot to recovery by holding volume up and power buttons until you see Mi logo on your screen (on device).
In LOS recovery:
do a factory reset first
go to "Factory reset" and perform "Format data / Factory reset"
all data will be erased. Then....
go to "Apply update", followed by "Apply from ADB"
Now sideload the ROM:
type in Windows Terminal
adb sideload lineage-19.1-20220617-UNOFFICIAL-cupid.zip
You can also drag ROM zip file into your terminal window, instead of typing the full name/path to file.
When finished, reboot simply your device.
ydd0ras said:
OK, I have wrote a flashing guide for Windows users, tho I don't use Windows so I hope all steps are correct:
Flashing LOS on Cupid
Xiaomi 12 LOS ROM flashing
Prerequisites:
Your bootloader must be unlocked.
You should use latest platform tools on Windows. https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Your device should be charged above 50%. Well, it doesn't have to be, but this is just for your phones safety.
Download all required files - ROM, boot, vendor_boot, dtbo and recovery.
Make a proper backup if needed and push it to another storage.
First steps:
After you have unlocked the bootloader, device will reboot automatically. Finish the setup, enable developer settings and finally enable USB-Debugging in developer settings.
In Windows open the folder in which you have unzipped the platform tools.
Hold left shift and press right click
click "open powershell window here"
Type in Terminal for example "adb devices" and grant the permissions for this PC on your device.
Reboot your device to fastboot and connect it with your PC.
The flashing procedure:
Flash boot, vendor_boot, dtbo and recovery:
Type in Windows Terminal:
fastboot flash boot lineage-19.1-20220617-UNOFFICIAL-cupid-boot.img
fastboot flash vendor_boot lineage-19.1-20220617-UNOFFICIAL-cupid-vendor_boot.img
fastboot flash dtbo_ab lineage-19.1-20220617-UNOFFICIAL-cupid-dtbo.img
fastboot flash recovery lineage-19.1-20220617-UNOFFICIAL-cupid-recovery.img
and finally
fastboot reboot recovery or
reboot to recovery by holding volume up and power buttons until you see Mi logo on your screen (on device).
In LOS recovery:
do a factory reset first
go to "Factory reset" and perform "Format data / Factory reset"
all data will be erased. Then....
go to "Apply update", followed by "Apply from ADB"
Now sideload the ROM:
type in Windows Terminal
adb sideload lineage-19.1-20220617-UNOFFICIAL-cupid.zip
You can also drag ROM zip file into your terminal window, instead of typing the full name/path to file.
When finished, reboot simply your device.
Click to expand...
Click to collapse
Is there a list of what's not working? That's be helpful for people who wants to know if the rom is suitable for daily drive.
Thank you!
Actually SMS don't come in. And D2W doesn't work. Maybe LOS needs to be polished a little. But I am using it for more than a week as daily driver. Put my Mi 11 lite 5G in the drawer.
ydd0ras said:
Actually SMS don't come in. And D2W doesn't work. Maybe LOS needs to be polished a little. But I am using it for more than a week as daily driver. Put my Mi 11 lite 5G in the drawer.
Click to expand...
Click to collapse
Your Info is really a great help! Thanks a lot!
Hi ! Do you have an idea of how I could contact the Dev of lineage for Xiaomi 12 ? I'd like to develop for Oneplus 10 pro and since they share the same soc he could be really useful