Related
Greetings, and a brief disclaimer;
--Disclaimer--
I am not responsible if you lose data or your device grows legs and runs away from you...
by following any of the instructions in this post, you take sole responsibility whatever happens to you or your device and any one else involved.
--Throughout this process we will be continuously wiping the device.--
--This tutorial flashes the International Firmware, you will not be running T-Mobiles Firmware.--
--If you want T-Mobiles Firmware this is not for you.--
---------------
Greetings fellow T-Mobile OnePlus 7 Pro Users and Developers!
I am excited after much frustration and beating my head against the wall, screaming profanities at T-Mobile & OnePlus for locking down this amazing phone.
Me and my Friend have FINALLY found out how to Bootloader Unlock, TWRP and ROOT the OnePlus 7 Pro from T-Mobile!
I know this is a longer guide, but that is because there were quite a few steps for the T-Mobile variant. A few snags were hit with the T-Mobile variant so that's why this guide is so lengthy.
The extra benefit of this guide is:
* You will have the DUAL SIM feature working. - I can confirm as I have placed two SIM's in the device and switched between them, T-Mobile disabled one of the OP 7 Pro SIM Slots, but with the Firmware Flash you get it back, I find that Flashing to International Firmware an important step as your getting a major feature of the device back. --Though you will need to buy a Dual SIM tray if you want to use two SIM's, this is where I bought mine: OnePlus 7 Pro DUAL SIM Tray
* You will get working Sound, if you go straight to Android Q from the flash and install TWRP * Magisk you will have audio issues. - I didn't think to test what else went wrong, but that I know did.
* DRM is working, I can stream Netflix content.
* Audio Fixes and Camera Features appear and sound great.
* I have not had stability issues such as crashes, reboot or other unwanted.
* WiFi, Bluetooth, DUAL GSM Radio's working properly.
* You can switch between the services of both SIM's properly via the pulldown menu, as well you can set up SIM defaults for particular actions.
* T-Mobiles VoLTE is working, as is VoWiFi. - Nice if your like me and live primarily in a basement apartment and get crap signal.
* You will not need to get T-Mobile's stupid Bootloader Unlock Token (BUT), that can take upwards of two weeks to get, to unlock the bootloader with this method. -- Skip the line, Yes please! I like skipping past BUT's.
--What you need to do first!--
You MUST get your phone Permanently CARRIER UNLOCKED BEFORE YOU ATTEMPT ANYTHING HERE!!!
----
--GUIDE--
1. I applied T-Mobiles: (9.5.9 Security Patch) I saw and installed it on July 23rd 2019 - This was needed in order to get the Flashing tool to work as it would get stuck on Param because without that patch the EDL would not allow the tool to flash the OnePlus 7 Pro.
2. I enabled ADB Debugging and used: TOOL ALL IN ONE to install my OnePlus 7 Pro Drivers, I also enabled Advanced Reboot in Developer Options.
2a. If you don't know how to enable Developer Options or ADB Debugging & Advanced Reboot here is how...
2b. Go into Settings, About Phone, TAP Build Number until it pops up that you are a developer (if you have a password/fingerprint set up it will ask you to put it in.).
2c. Go to Settings, System, Advanced Options, Developer Options.
2d. Enable, Advanced Reboot, USB Debugging.
3. I followed the Tutorial on this link to install the International Firmware (WARNING THIS WILL WIPE YOUR Phones DATA!!!): [GUIDE]How to convert TMobile OP7 to International.
4. I then updated the phone through the phones OTA updater via Settings, System, System Updates all the way until it had no more updates. ( If we installed Android Q before this we found that the speaker had issues during a Google Duo call. So something about how this all stacks and builds up together breaks if you don't do this in order.)
5. We then downloaded and placed: Android Q Beta onto the root of the OnePlus 7 Pro storage.
5a I went to Settings, System, System Update, Options, Local Upgrade.
5b If you have the Android Q firmware in the right place you will get that as an option to flash, once it's done click the button to reboot.
6. Unlocking the Bootloader.
6a. Enable Developer Options.
6b. Now we enable OEM Unlocking, and Advanced Reboot if not already. ( If you did not previously get your device Permanently SIM Unlocked you will not be able to enable OEM Unlocking, and you will be stuck unless you flash back to T-Mobile's Firmware and use their proprietary SIM Unlock APP. ).
6c. Press power button and reboot to Bootloader.
6d. Run the command ( fastboot oem unlock ). It should ask you on the phones screen if you want to, say yes.
6e. Run the command ( fastboot oem device-info ). Check to see if the bootloader unlock is True or False, True is expected. If False unlock the bootloader via other methods.
7. Booting TWRP & Flashing TWIRP + Magisk.
This was a bit tricky as the existing tutorials did not work with my device and I had to add a step.
First get the TWRP.IMG & TWRP Installer ZIP files ready as well grab Magisk by downloading them here: Official/Unofficial TWRP recovery for OnePlus 7 Pro. & Magisk
7a. Run the command ( fastboot boot TWRP.IMG ) The phone should then boot into what looks like full TWRP, well sorta, it's not really installed yet.
7b. If 7a fails as it did with me Run the Command ( fastboot set_active b ) then try 7a command again, if that fails as well run ( fastboot set_active a ). and repeat.
7c. Once you have booted TWRP put the TWRP installer ZIP on the phone in the root directory.
7d. Now we get the Magisk installer zip on the root of the phone as well.
7e. Now we install TWRP installer ZIP first then Magisk installer ZIP.
Reboot - Enjoy and install custom ROMs & Kernels!
--reserved--
<Mod edit - quoted OP removed>
I get the failed message you talk about in step 7b. When I try to run the commands "fastboot set_active b" it doesn't recognize that command or the other to set to a. I'm stuck not being able to install TWRP and proceed to root. Any ideas?
kevnfl77 said:
<Mod edit - quoted OP removed>
I get the failed message you talk about in step 7b. When I try to run the commands "fastboot set_active b" it doesn't recognize that command or the other to set to a. I'm stuck not being able to install TWRP and proceed to root. Any ideas?
Click to expand...
Click to collapse
I'm having the same issue, though I didnt carrier unlock my phone. Have you done that?
---------- Post added at 07:53 PM ---------- Previous post was at 07:35 PM ----------
@Inductive Soul would appreciate any feedback you might have regarding this. I followed the process using the Q Preview 3
weakNPCdotCom said:
I'm having the same issue, though I didnt carrier unlock my phone. Have you done that?
---------- Post added at 07:53 PM ---------- Previous post was at 07:35 PM ----------
@Inductive Soul would appreciate any feedback you might have regarding this. I followed the process using the Q Preview 3
Click to expand...
Click to collapse
Yes I was carrier unlocked.
If anybody comes here looking to root, this guide does not work. You need to follow the guide to convert to international
Help please, unlocked bootloader and tried to install twrp image. Screen stayed stuck on fastboot screen with the one + symbol.?
I was wondering if network bands change after flashing to international rom. Will it continue to be NA region or will it change?
Correct you need to first flash to international version. Then use this guide.
Tool ALL in one does not work anymore with this phone. - I recommend you do not use this method any more as its method I used will no longer work.
weakNPCdotCom said:
If anybody comes here looking to root, this guide does not work. You need to follow the guide to convert to international
Click to expand...
Click to collapse
kevnfl77 said:
<Mod edit - quoted OP removed>
I get the failed message you talk about in step 7b. When I try to run the commands "fastboot set_active b" it doesn't recognize that command or the other to set to a. I'm stuck not being able to install TWRP and proceed to root. Any ideas?
Click to expand...
Click to collapse
Yes, change it back and forth (Your goal is to get Fastboot Boot TWRP.IMg to boot.... so switch your active... A-B partition with step 7b and try 7a again on each partition.... a and b. one or the other will work depending on what partition is currently active.):
7A: fastboot boot TWRP.IMG
7B: fastboot set_active a - to - fastboot set_active b
gearmaker said:
I was wondering if network bands change after flashing to international rom. Will it continue to be NA region or will it change?
Click to expand...
Click to collapse
My experience has been that all the existing bands have worked the same... I have continued to connect to T-Mobile's 600 + 700 Mhz spectrum.
I have been running the International Firmware since the initial posting of this guide.
I thought that they would be the same after flashing.Just wanted to confirm.
Thank you
Just got this phone today, and I just want to make sure I'm clear. If I go through these steps, I'll be on Q DP3, but I don't need to go through the waiting period via T-Mobile (I bought my phone outright) but after I get on DP3, can I then flash the International stock ROM and be good, or will I always have to use a custom ROM after doing these steps?? I saw somewhere that Bootloader unlocked is grayed out after you go to DP3 and then International ROMs. Thanks.
Hi, On my T-Mobile O7pro
I tried the command
Fastboot boot TWRP.img
It replaced my stock boot image and now I can't boot again, even to the supposed TWRP recovery
I also switched partitions countless times and tried same process.
I'll appreciate if I get a feedback. Thanks
Hi,
Please someone experienced a black screen in Qhd and 90Hz after doing that, in the 11.0.2.* ??
thx in advance.
This is an entertaining and educational review of degoogling my first android device.
The Goal: A LineageOS device without GAPPS, with TWRP, Magisk, and MicroG
Finding a phone that is available new in Australia, has a decent camera, and supports both TWRP and LineageOS officially is a suprisingly hard ask. After a couple of days of cross-referencing and researching I found one device: the Xiaomi Redmi Note 8.
In the days before the delivery of this new phone, I pieced together a guide for installing everything I needed in nice step by step order, I downloaded everything I thought I would need, TWRP, LineageOS, Magisk both apk and zip, MicroG, and the SmaliPatcher, as well as the Mi Unlocker and USB Drivers, and I made a Mi account hooked up to an email address. I was prepared, everything was set up for smooth sailing.
As we all know, things rarely turn out so easy.
The first hurdle was unlocking the bootloader. In order to unlock the bootloader, you have to unlock Developer Options and enable OEM Unlocking, USB Debugging, and USB Debugging (Security Settings). I'm not stuttering, there are two USB Debuggings. I had unlocked Developer Permissions on my Smart E9 before, but that runs Oreo Go edition, and in that one you have to go Settings -> About and tap the build version 7 times. In a Xiaomi, you have to tap MIUI version 7 times. This is not obvious, as 'build version' is also visible in 'About'.
Quick Guide: Go to Settings -> About and tap MIUI version 7 times to enable Developer Options
Click to expand...
Click to collapse
Enabling the correct permissions was also not so simple. Enabling OEM Unlocking and USB Debugging was as simple as tapping the switches, but USB Debugging (Security Settings) has three seperate warning popups and only lets you know you NEED a Sim card AFTER you've tapped through.
The Redmi Note 8 takes Nano Sims. I only have my regular sized Sim. So, on the phone with my carrier I go to order a replacement Nano Sim. After a frustrating conversation online in which they tell me to ring my local branch and won't give me the number, I ring my local branch. Who then won't replace it unless I come in, which I point blank refuse to do due to the whole plague situation. I decide to phone the main branch, who tells me they'll send a replacement out right away free of charge. Okay then.
To insert the Sim (And a MicroSD if you want) there's a small hole in left the side of the phone, where you stick the little pokey key thing that comes with the phone (A paperclip is too thick), and the Sim tray pops out. The Sim and SD card just sit on the tray, balanced precariously, as you gently stuff that tray back where it came from.
Quick Guide: Argue with underpaid customer service reps for an hour to get your Nano Sim card
Click to expand...
Click to collapse
Sim inserted successfully, so now I try to enable USB Debugging (Security Settings) again. Tap through the three warning popups and success! All permissions were now set, and it was time to unlock the bootloader!
Quick Guide: After inserting a working Nano Sim, go to Settings -> Developer Settings, and enable OEM Unlocking, USB Debugging, and USB Debugging (Security Settings)
Click to expand...
Click to collapse
I turn off the phone, boot into fastboot, log into the Mi Unlock App on the PC and...
Turns out: You have to have a recovery phone number for the Mi Account before you can see any unlocking options on the PC App. I guess the chinese government has my phone number now.
Quick Guide: Set up a Mi Account with both an email address and a phone number
Click to expand...
Click to collapse
So, after setting up that recovery phone number on the website I tried again, log the phone into fastboot, log into the Mi Unlock App, plug in the phone and...
I get told to use the Mi Unlock Status option on the phone to unlock the option to unlock. Huh. Fine then.
This is where things get a little bit more ring around the rosy, because I had already hooked the Mi Account up to the phone and logged in, for some reason the Mi Unlock Status option in the phone point blank refused to log in using mobile data. I logged out of the Mi Account on the phone, rebooted the phone, and then tapped straight through to the Mi Unlock Status, logging in there using Mobile Data. It worked this time!
Quick Guide: Choose Mi Unlock Status and tap through, turn off Wi-Fi and turn on Mobile Data, log into the Mi account, then go back a screen and press the button
Click to expand...
Click to collapse
NOW it was time to use the Mi Unlock App. I opened it up, signed in to the Mi Account, and received a verification SMS on the phone. Verification dealt with, I turned off the phone, logged it into fastboot, use the USB to connect to the PC, and press Unlock. Success! Well, sort of. I get told I need to wait 168 hours before I can unlock the bootloader, but progress is progress.
Quick Guide: Open up the Mi Unlock App and sign in, shut down your phone, hold Volume Down + Power to enter Fastboot. Then connect your phone to PC using USB cable and click "Unlock"
Click to expand...
Click to collapse
Waiting 168 hours (7 days) to play with a new toy is difficult. I also had to make sure I kept using the device during this time. I browsed reddit and mi community for a few minutes a day and played a bit of tetris. Other than that the phone was left on but idle. This is an example of bare minimum usage because A: I'm not really a phone person, I'm a PC person, and B: At this point I am referring to my phone as 'the spy machine' due to just how utterly violating of privacy I know this thing to be. Thus the degoogling.
After waiting the requisite amount of time it was time to ACTUALLY unlock the bootloader. At this point I was regretting not buying a Motorola G7, but I couldn't have purchased one new anyway.
So again, I open the Mi Unlock App, sign in, boot the phone into fastboot, and plug that sucker in. Press Unlock. Success! Actual success this time, bootloader is unlocked. It reboots and has a little unlock symbol at the bottom of the screen. When the phone boots up, it asks for my Mi Account password before it will set up the OS again. No problem.
Quick Guide: Repeat the previous Unlocking procedure, then enter your Mi Password into the phone if it asks
Click to expand...
Click to collapse
Now it was time for TWRP. Developer Options and both kinds of USB Debugging had been reset after unlocking the bootloader, so they all had to be enabled again.
I copy the TWRP recovery image into my platform-tools folder and open a command prompt in said folder. I connect my phone to the PC, and in the command window I type
Code:
adb devices
. It lists the devices, which is to say none. Freaking what.
I read a couple of guides. Okay, drivers are needed. The Mi Unlock App straight up came with the necessary drivers so, double clicky the USB drivers exe and boom. All fixed.
Code:
adb devices
now lists my phone and it's unauthorized. Back to the phone, allow this computer and press the checkbox for always allow it. Now it's authorized.
Quick Guide: Install your goddamn USB drivers
Click to expand...
Click to collapse
Now that ADB is working it's time to install TWRP. I reboot the phone into fastboot using the command window with
Code:
adb reboot bootloader
. I'm not sure its actually necessary to boot into fastboot this way, I'm pretty sure doing it manually while it's plugged in works just fine, but that's what the guide said and at this point I am too nervous to deviate.
Alright, now the phone is in fastboot and I still have a command window up. I make sure the device is still connected with
Code:
adb devices
Nothing. Okay what now, oh, oopsie. Turns out that's the wrong command when in fastboot. Okay
Code:
fastboot devices
That's much better.
Now I type
Code:
fastboot flash recovery twrp-3.4.0-1-ginkgo.img
Successfully flashed, now to boot into it.
Code:
fastboot boot twrp-3.4.0-1-ginkgo.img
The phone booted into TWRP! I am excited, I'd never gotten this far before.
Quick Guide: Boot into fastboot. Check the connection with
Code:
fastboot devices
Flash the recovery with
Code:
fastboot flash recovery <yourrecoveryname>.img
Boot into the recovery with
Code:
fastboot boot <yourrecoveryname>.img
Click to expand...
Click to collapse
With TWRP flashed it was time for LineageOS. This was a little odd because to install it, the guide said to 'sideload' the zip file, and I had no idea what this actually meant. But, it had step by step instructions, and you don't learn unless you try. Onwards I went.
First, I move the LineageOS zip file to my platform-tools directory. Then I use TWRP to make a backup, then I head back to the home screen, press wipe, and format data. Don't ask me why I did this, it was in my guide and I'm pretty sure a youtube video told me to. I don't think this step is necessary, and quite frankly the_weird_aquarian's guide says it's not recommended.
Now it was time to actually sideload the LineageOS zip. On the TWRP home screen, I choose Advanced -> ADB Sideload and swipe the little slider. On the command window I type
Code:
adb sideload lineage-17.1-20201026-nightly-ginkgo-signed.zip
I didn't actually type out that whole zip name by hand, that'd be ridiculous, I pressed tab to autofill it after typing "lin". This step took a while to finish.
Quick Guide: Choose Advanced -> ADB Sideload, then in the command windows type
Code:
adb sideload <customromname>.zip
Click to expand...
Click to collapse
After it was done, it offered to reboot. This was it. I rebooted and there it was, the LineageOS system. I had done the bulk of it!
(I had not done the bulk of it)
One thing I immediately noticed was that the little triangle and little square symbols for navigation were reversed from what they were in MIUI (original xiaomi phone OS).
I played with the device for a while, installed F-Droid and a few apps, made sure I could still make phone calls, that sort of thing.
Next it was time to install Magisk. First I needed to set the permissions again. This time 'build number' is the thing to tap, right at the bottom of the About page.
Quick Guide: Go to Settings -> About -> tap Build Number 7 times
Click to expand...
Click to collapse
Developer Options are in a different spot in LineageOS, this time they're under Settings -> System -> Advanced, and now I enable Android Debugging, which is the same as USB Debugging but everyone needs their own name for it.
Quick Guide: Go to Settings -> System -> Advanced and enable Android Debugging
Click to expand...
Click to collapse
Now I transfer the Magisk apk and zip file onto the phone and install the apk. Opening up the app, I notice that it says "ramdisk: no". The Magisk Wiki says that if my device’s boot partition does not include ramdisk, I have to patch Magisk into the TWRP recovery, and it has instructions on how to do that.
I grab the TWRP image and copy it onto the phone, then go back into the Magisk Manager app and press 'Install' on the Magisk card. I make sure 'Recovery' is checked, choose the 'Select and Patch a File' option and pick said recovery image.
After it finished patching, I pull it back to the computer with
Code:
adb pull /sdcard/Download/magisk_patched.img
Then I reboot the phone into fastboot and flash this patched recovery with
Code:
fastboot flash recovery magisk_patched.img
After rebooting I check the Magisk Manager app, which reports that Magisk was NOT installed. Okay, so the Wiki says that in order to boot into the Magisk system I have to hold down Volume Up + Power just like I would if I was booting into recovery, but then let go of everything after the splash screen. Okay, I do that.
It boots to fastboot. Huh, odd. Okay, I turn the phone off and try it again. It boots normally this time, but Magisk is still not installed. I looked up the problem, Magisk Manager didn't install twice, it wasn't installed to external storage, I reinstalled the Manager and it didn't help.
I had nothing. No idea at all. I gave it a break for a day.
Quick Guide: Don't do anything that I did in the above section
Click to expand...
Click to collapse
This was when I encountered one thing I really didn't like about LineageOS: the Camera.
The default LineageOS Camera is not great. The pictures are fine, but the Redmi Note 8 comes with a macro lens, an ultrawide lens, and the ability to do panorama shots. None of these were accessible in the default camera.
I tried Open Camera and FreeDCam, I didn't like either of them. Camera MX wasn't available on Aurora Store.
So after some googling I came to what was to be my saviour: ANXCamera. It's the MIUI Camera App, retrofitted for Custom ROMs.
There was one problem: It needed Magisk.
Back to XDA I go, back to the beginners guides. Specifically the_weird_aquarian's guide. Here, the instructions for Magisk were different. These said to just install the zip from inside TWRP. The Wiki said this was not recommended. I do it anyway.
I rebooted, crossing my fingers. It booted, a good start. I tapped into the Magisk App and... "Installed". I had done it!
Quick Guide: Boot into TWRP, press install, pick the Magisk zip, and reboot
Click to expand...
Click to collapse
Now I had to figure out how to install the two modules I had downloaded: ANXCamera and ANXFramework. It's simple after Magisk is actually installed, there's a little puzzle piece logo on the bottom right for AddOns. Next, I install both modules and reboot, excited for a new camera.
Then, disaster struck. I bootlooped.
The first step was obviously to panic, which I did with great diligence and enthusiasm. Then I boot into the recovery and try to restore from the backup I made. Only to discover that there was no backup there. It had gotten deleted when I wiped the device the first time.
Quick Guide: Save a copy of backups externally just in case
Click to expand...
Click to collapse
I googled and found a bootloop hotfix addon for ANXCamera, listed in bold right on the page where I downloaded the other modules. But it needed to be installed in Magisk, and I didn't have access to Magisk.
Next, I tried to 'reinstall' LineageOS by sideloading it again. This did absolutely squat diddly.
Factory reset came to the rescue.
It was only after this that I found that the ANXCamera wiki straight up tells you that if you bootloop you should use the recovery file manager to remove '/data/adb/modules/ANXFramework' and '/data/adb/modules/ANXCamera'. Oh well.
My phone was working again, but all my apps and contacts had been deleted. Strangely, all the pictures I'd taken and all the files I had transferred to the phone were untouched. I wasn't about to look a gift horse in the mouth.
I reinstalled Magisk Manager, determined to get this camera app working. It said Magisk was already installed, and that it needed to download and install a few files to get everything working. Alrighty, no worries there. I let it reboot and hoped really hard that it wasn't about to reinstall the modules that had bootlooped my phone the first time.
It didn't. The files were technically there, but they weren't counted as installed in the AddOn's section of Magisk's Manager. I reinstall them, along with the bootloop fix and a 48MP fix. It rebooted. No bootloop. Everything was okay.
Quick Guide: Read everything before jumping the gun. If something says it needs a bootloop hotfix, believe it
Click to expand...
Click to collapse
Quick Guide: Install ANXCamera, ANXFramework, ANXCamera bootloop hotfix, and the 48MP fix in Magisk's AddOns section
Click to expand...
Click to collapse
Now I needed the actual camera app, because this wasn't complicated enough yet. So, I install F-Droid, and then install Aurora Store from F-Droid, and, in Aurora Store, I find the ANX Camera Pro app. I install that, open it up and press save, then start up the actual camera app. Everything was black. It wasn't working. I had to enable all the permissions for the app manually.
Quick Guide: Go to Settings -> Apps -> See All -> ANXCamera and enable all the permissions. Turn off network access for it while you're there, it doesn't need the net
Click to expand...
Click to collapse
Sweet, no more black screen. Everything looked good! Then I tried the front camera, and it crashed. Damn. Okay, the FAQ says to hop back into ANXCamera Pro and turn off Hand Gestures. I do that, and the front camera works now, awesome.
Portrait mode crashed the app again. The 48MP fix was supposed to fix that. Okay, uninstall that and install an older version... nothing. Uninstall that and install ANXCustlibs instead. Nothing. Installed the latest version of 48MP fix. Still nope.
I could not get portrait mode working at all, it just crashes the camera app every time. Everything else works nicely, so I just moved that mode out of the main section in the app's own settings.
I still haven't installed MicroG. I haven't found a good reason to install it, and truth be told I am a little scared of what traps and tripwires lie in wait on that particular journey. One day I will make it, but for now, I have a degoogled phone.
I read your post with a smile, because I also had my trial and errors for the simple very first step to unlock the bootloader.
But all later issues you described from unlocking till having a custom ROM were fortunately NOT discovered by me:
I chose to use MSMXtended as custom rom since my feeling of that rom after heaving read several custom rom threads including Lineage OS was that MSMXtended is really stable and easy to flash.
I am speaking of the meanwhile closed thread for MSMXtended running Android 10 (!) with it's latest version 13. Give it a try and follow the very simple steps (but do not forget to flash dm-verity zip at the end before rebooting).
You will have a very smooth, google-free rom with the stock MIUI-cam and a very battery friendly behaviour. I was also able to install the famous GCam without (!) the need to install gapps (I have described this elsewhere).
During the weekend I have prepared two more Redmi Note 8 for MSMXtended v13 (for my father and for my daughter) and everything works fine. By the way I also installed EdXposed and XPrivacy Lua for privacy reasons - everything working as I expected (or better: hoped).
And one more hint: during the 168 days waiting time for unlocking the bootloader there is NO need to do anything with the phone. You can remove the SIM-card, you can shut-down the phone. The only important thing us that you MUST NOT log-out your phone from your MIUI-account.
I hope that other readers are not too frightened from the odyssey you described. ..
JellyfishSprinkle said:
too much hahahaha ...
Click to expand...
Click to collapse
waste of time
Uluru25 said:
I read your post with a smile, because I also had my trial and errors for the simple very first step to unlock the bootloader.
But all later issues you described from unlocking till having a custom ROM were fortunately NOT discovered by me:
I chose to use MSMXtended as custom rom since my feeling of that rom after heaving read several custom rom threads including Lineage OS was that MSMXtended is really stable and easy to flash.
I am speaking of the meanwhile closed thread for MSMXtended running Android 10 (!) with it's latest version 13. Give it a try and follow the very simple steps (but do not forget to flash dm-verity zip at the end before rebooting).
You will have a very smooth, google-free rom with the stock MIUI-cam and a very battery friendly behaviour. I was also able to install the famous GCam without (!) the need to install gapps (I have described this elsewhere).
During the weekend I have prepared two more Redmi Note 8 for MSMXtended v13 (for my father and for my daughter) and everything works fine. By the way I also installed EdXposed and XPrivacy Lua for privacy reasons - everything working as I expected (or better: hoped).
And one more hint: during the 168 days waiting time for unlocking the bootloader there is NO need to do anything with the phone. You can remove the SIM-card, you can shut-down the phone. The only important thing us that you MUST NOT log-out your phone from your MIUI-account.
I hope that other readers are not too frightened from the odyssey you described. ..
Click to expand...
Click to collapse
Thank you for the recommendations and the info. I'd not heard of XPrivacy Lua before, it sounds really cool. I am going to be taking a step back and looking at other ROM options, I chose LineageOS because it's the most well known privacy ROM for android, but I know that doesn't mean it's necessarily the best option.
Thank you also for letting me know that I can just let the phone sit there during the unlocking period, that'll make life a lot easier in the future.
May I ask why one needs to flash dm-verity after installing MSMXtended? I don't really understand what it does.
loopypalm said:
i didn't read tbh ...
Click to expand...
Click to collapse
I don't take advice from people who couldn't be bothered to read what they're advising on!
Common courtesy goes a long way. You should try it sometime.
JellyfishSprinkle said:
Thank you for the recommendations and the info. I'd not heard of XPrivacy Lua before, it sounds really cool. I am going to be taking a step back and looking at other ROM options, I chose LineageOS because it's the most well known privacy ROM for android, but I know that doesn't mean it's necessarily the best option.
Thank you also for letting me know that I can just let the phone sit there during the unlocking period, that'll make life a lot easier in the future.
May I ask why one needs to flash dm-verity after installing MSMXtended? I don't really understand what it does.
Click to expand...
Click to collapse
From my understanding if you use a custom rom which does not support encryption (as it is true for MSMXtended) your device might refrain from booting but will return to the recovery. This dm-verity zip (flashed at the very last before rebooting) prevents this. But I am not an expert but only an "interested reader". You will find a big post hier in xda by zackpfg5 as OP or a short note in the very first post in The-weird-aquarian's guide to unlocking and for sure elsewhere in the web. Maybe you don't need it but better have it on your sd-card in case your phone doesn't boot after flashing the custom rom. Good Luck!
Without meaning to belittle JellyfishSprinkle's impressive work, quick note to the less hacking inclined:
/e/ Foundation Lineage based OS including microG now supports gingko/willow devices natively (see https://doc.e.foundation/devices/ginkgo/).
Love your post!
JellyfishSprinkle said:
This is an entertaining and educational review of degoogling my first android device.
The Goal: A LineageOS device without GAPPS, with TWRP, Magisk, and MicroG
Finding a phone that is available new in Australia, has a decent camera, and supports both TWRP and LineageOS officially is a suprisingly hard ask. After a couple of days of cross-referencing and researching I found one device: the Xiaomi Redmi Note 8.
In the days before the delivery of this new phone, I pieced together a guide for installing everything I needed in nice step by step order, I downloaded everything I thought I would need, TWRP, LineageOS, Magisk both apk and zip, MicroG, and the SmaliPatcher, as well as the Mi Unlocker and USB Drivers, and I made a Mi account hooked up to an email address. I was prepared, everything was set up for smooth sailing.
As we all know, things rarely turn out so easy.
The first hurdle was unlocking the bootloader. In order to unlock the bootloader, you have to unlock Developer Options and enable OEM Unlocking, USB Debugging, and USB Debugging (Security Settings). I'm not stuttering, there are two USB Debuggings. I had unlocked Developer Permissions on my Smart E9 before, but that runs Oreo Go edition, and in that one you have to go Settings -> About and tap the build version 7 times. In a Xiaomi, you have to tap MIUI version 7 times. This is not obvious, as 'build version' is also visible in 'About'.
Enabling the correct permissions was also not so simple. Enabling OEM Unlocking and USB Debugging was as simple as tapping the switches, but USB Debugging (Security Settings) has three seperate warning popups and only lets you know you NEED a Sim card AFTER you've tapped through.
The Redmi Note 8 takes Nano Sims. I only have my regular sized Sim. So, on the phone with my carrier I go to order a replacement Nano Sim. After a frustrating conversation online in which they tell me to ring my local branch and won't give me the number, I ring my local branch. Who then won't replace it unless I come in, which I point blank refuse to do due to the whole plague situation. I decide to phone the main branch, who tells me they'll send a replacement out right away free of charge. Okay then.
To insert the Sim (And a MicroSD if you want) there's a small hole in left the side of the phone, where you stick the little pokey key thing that comes with the phone (A paperclip is too thick), and the Sim tray pops out. The Sim and SD card just sit on the tray, balanced precariously, as you gently stuff that tray back where it came from.
Sim inserted successfully, so now I try to enable USB Debugging (Security Settings) again. Tap through the three warning popups and success! All permissions were now set, and it was time to unlock the bootloader!
I turn off the phone, boot into fastboot, log into the Mi Unlock App on the PC and...
Turns out: You have to have a recovery phone number for the Mi Account before you can see any unlocking options on the PC App. I guess the chinese government has my phone number now.
So, after setting up that recovery phone number on the website I tried again, log the phone into fastboot, log into the Mi Unlock App, plug in the phone and...
I get told to use the Mi Unlock Status option on the phone to unlock the option to unlock. Huh. Fine then.
This is where things get a little bit more ring around the rosy, because I had already hooked the Mi Account up to the phone and logged in, for some reason the Mi Unlock Status option in the phone point blank refused to log in using mobile data. I logged out of the Mi Account on the phone, rebooted the phone, and then tapped straight through to the Mi Unlock Status, logging in there using Mobile Data. It worked this time!
NOW it was time to use the Mi Unlock App. I opened it up, signed in to the Mi Account, and received a verification SMS on the phone. Verification dealt with, I turned off the phone, logged it into fastboot, use the USB to connect to the PC, and press Unlock. Success! Well, sort of. I get told I need to wait 168 hours before I can unlock the bootloader, but progress is progress.
Waiting 168 hours (7 days) to play with a new toy is difficult. I also had to make sure I kept using the device during this time. I browsed reddit and mi community for a few minutes a day and played a bit of tetris. Other than that the phone was left on but idle. This is an example of bare minimum usage because A: I'm not really a phone person, I'm a PC person, and B: At this point I am referring to my phone as 'the spy machine' due to just how utterly violating of privacy I know this thing to be. Thus the degoogling.
After waiting the requisite amount of time it was time to ACTUALLY unlock the bootloader. At this point I was regretting not buying a Motorola G7, but I couldn't have purchased one new anyway.
So again, I open the Mi Unlock App, sign in, boot the phone into fastboot, and plug that sucker in. Press Unlock. Success! Actual success this time, bootloader is unlocked. It reboots and has a little unlock symbol at the bottom of the screen. When the phone boots up, it asks for my Mi Account password before it will set up the OS again. No problem.
Now it was time for TWRP. Developer Options and both kinds of USB Debugging had been reset after unlocking the bootloader, so they all had to be enabled again.
I copy the TWRP recovery image into my platform-tools folder and open a command prompt in said folder. I connect my phone to the PC, and in the command window I type
Code:
adb devices
. It lists the devices, which is to say none. Freaking what.
I read a couple of guides. Okay, drivers are needed. The Mi Unlock App straight up came with the necessary drivers so, double clicky the USB drivers exe and boom. All fixed.
Code:
adb devices
now lists my phone and it's unauthorized. Back to the phone, allow this computer and press the checkbox for always allow it. Now it's authorized.
Now that ADB is working it's time to install TWRP. I reboot the phone into fastboot using the command window with
Code:
adb reboot bootloader
. I'm not sure its actually necessary to boot into fastboot this way, I'm pretty sure doing it manually while it's plugged in works just fine, but that's what the guide said and at this point I am too nervous to deviate.
Alright, now the phone is in fastboot and I still have a command window up. I make sure the device is still connected with
Code:
adb devices
Nothing. Okay what now, oh, oopsie. Turns out that's the wrong command when in fastboot. Okay
Code:
fastboot devices
That's much better.
Now I type
Code:
fastboot flash recovery twrp-3.4.0-1-ginkgo.img
Successfully flashed, now to boot into it.
Code:
fastboot boot twrp-3.4.0-1-ginkgo.img
The phone booted into TWRP! I am excited, I'd never gotten this far before.
With TWRP flashed it was time for LineageOS. This was a little odd because to install it, the guide said to 'sideload' the zip file, and I had no idea what this actually meant. But, it had step by step instructions, and you don't learn unless you try. Onwards I went.
First, I move the LineageOS zip file to my platform-tools directory. Then I use TWRP to make a backup, then I head back to the home screen, press wipe, and format data. Don't ask me why I did this, it was in my guide and I'm pretty sure a youtube video told me to. I don't think this step is necessary, and quite frankly the_weird_aquarian's guide says it's not recommended.
Now it was time to actually sideload the LineageOS zip. On the TWRP home screen, I choose Advanced -> ADB Sideload and swipe the little slider. On the command window I type
Code:
adb sideload lineage-17.1-20201026-nightly-ginkgo-signed.zip
I didn't actually type out that whole zip name by hand, that'd be ridiculous, I pressed tab to autofill it after typing "lin". This step took a while to finish.
After it was done, it offered to reboot. This was it. I rebooted and there it was, the LineageOS system. I had done the bulk of it!
(I had not done the bulk of it)
One thing I immediately noticed was that the little triangle and little square symbols for navigation were reversed from what they were in MIUI (original xiaomi phone OS).
I played with the device for a while, installed F-Droid and a few apps, made sure I could still make phone calls, that sort of thing.
Next it was time to install Magisk. First I needed to set the permissions again. This time 'build number' is the thing to tap, right at the bottom of the About page.
Developer Options are in a different spot in LineageOS, this time they're under Settings -> System -> Advanced, and now I enable Android Debugging, which is the same as USB Debugging but everyone needs their own name for it.
Now I transfer the Magisk apk and zip file onto the phone and install the apk. Opening up the app, I notice that it says "ramdisk: no". The Magisk Wiki says that if my device’s boot partition does not include ramdisk, I have to patch Magisk into the TWRP recovery, and it has instructions on how to do that.
I grab the TWRP image and copy it onto the phone, then go back into the Magisk Manager app and press 'Install' on the Magisk card. I make sure 'Recovery' is checked, choose the 'Select and Patch a File' option and pick said recovery image.
After it finished patching, I pull it back to the computer with
Code:
adb pull /sdcard/Download/magisk_patched.img
Then I reboot the phone into fastboot and flash this patched recovery with
Code:
fastboot flash recovery magisk_patched.img
After rebooting I check the Magisk Manager app, which reports that Magisk was NOT installed. Okay, so the Wiki says that in order to boot into the Magisk system I have to hold down Volume Up + Power just like I would if I was booting into recovery, but then let go of everything after the splash screen. Okay, I do that.
It boots to fastboot. Huh, odd. Okay, I turn the phone off and try it again. It boots normally this time, but Magisk is still not installed. I looked up the problem, Magisk Manager didn't install twice, it wasn't installed to external storage, I reinstalled the Manager and it didn't help.
I had nothing. No idea at all. I gave it a break for a day.
This was when I encountered one thing I really didn't like about LineageOS: the Camera.
The default LineageOS Camera is not great. The pictures are fine, but the Redmi Note 8 comes with a macro lens, an ultrawide lens, and the ability to do panorama shots. None of these were accessible in the default camera.
I tried Open Camera and FreeDCam, I didn't like either of them. Camera MX wasn't available on Aurora Store.
So after some googling I came to what was to be my saviour: ANXCamera. It's the MIUI Camera App, retrofitted for Custom ROMs.
There was one problem: It needed Magisk.
Back to XDA I go, back to the beginners guides. Specifically the_weird_aquarian's guide. Here, the instructions for Magisk were different. These said to just install the zip from inside TWRP. The Wiki said this was not recommended. I do it anyway.
I rebooted, crossing my fingers. It booted, a good start. I tapped into the Magisk App and... "Installed". I had done it!
Now I had to figure out how to install the two modules I had downloaded: ANXCamera and ANXFramework. It's simple after Magisk is actually installed, there's a little puzzle piece logo on the bottom right for AddOns. Next, I install both modules and reboot, excited for a new camera.
Then, disaster struck. I bootlooped.
The first step was obviously to panic, which I did with great diligence and enthusiasm. Then I boot into the recovery and try to restore from the backup I made. Only to discover that there was no backup there. It had gotten deleted when I wiped the device the first time.
I googled and found a bootloop hotfix addon for ANXCamera, listed in bold right on the page where I downloaded the other modules. But it needed to be installed in Magisk, and I didn't have access to Magisk.
Next, I tried to 'reinstall' LineageOS by sideloading it again. This did absolutely squat diddly.
Factory reset came to the rescue.
It was only after this that I found that the ANXCamera wiki straight up tells you that if you bootloop you should use the recovery file manager to remove '/data/adb/modules/ANXFramework' and '/data/adb/modules/ANXCamera'. Oh well.
My phone was working again, but all my apps and contacts had been deleted. Strangely, all the pictures I'd taken and all the files I had transferred to the phone were untouched. I wasn't about to look a gift horse in the mouth.
I reinstalled Magisk Manager, determined to get this camera app working. It said Magisk was already installed, and that it needed to download and install a few files to get everything working. Alrighty, no worries there. I let it reboot and hoped really hard that it wasn't about to reinstall the modules that had bootlooped my phone the first time.
It didn't. The files were technically there, but they weren't counted as installed in the AddOn's section of Magisk's Manager. I reinstall them, along with the bootloop fix and a 48MP fix. It rebooted. No bootloop. Everything was okay.
Now I needed the actual camera app, because this wasn't complicated enough yet. So, I install F-Droid, and then install Aurora Store from F-Droid, and, in Aurora Store, I find the ANX Camera Pro app. I install that, open it up and press save, then start up the actual camera app. Everything was black. It wasn't working. I had to enable all the permissions for the app manually.
Sweet, no more black screen. Everything looked good! Then I tried the front camera, and it crashed. Damn. Okay, the FAQ says to hop back into ANXCamera Pro and turn off Hand Gestures. I do that, and the front camera works now, awesome.
Portrait mode crashed the app again. The 48MP fix was supposed to fix that. Okay, uninstall that and install an older version... nothing. Uninstall that and install ANXCustlibs instead. Nothing. Installed the latest version of 48MP fix. Still nope.
I could not get portrait mode working at all, it just crashes the camera app every time. Everything else works nicely, so I just moved that mode out of the main section in the app's own settings.
I still haven't installed MicroG. I haven't found a good reason to install it, and truth be told I am a little scared of what traps and tripwires lie in wait on that particular journey. One day I will make it, but for now, I have a degoogled phone.
Click to expand...
Click to collapse
I appreciate the time and effort you exerted to record and post your experiences! Thank you!
(I bookmarked your post so I can study it and LEARN from it!)
yeah, all the world must degoogle own phone, and all sites must publish the apk on the own portal, not on the Gplaystore.
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX2001, RMX2002 and RMX2003 ONLY. DON'T DO ANY OF THESE IF YOU HAVE SOMETHING ELSE!
PLEASE SEE "TROUBLESHOOTING" AT THE END OF THE GUIDE FIRST IF YOU HAVE PROBLEMS IN THE PROCESS BEFORE ASKING!
ALWAYS USE DOWNLOAD ONLY MODE OF SP FLASH TOOL.
DON'T TOUCH ANYTHING RELATED TO FORMAT ON SP FLASH TOOL! (IT'S WRITTEN EVERYWHERE, YOU WILL LOSE YOUR IMEIS IF YOU USE FORMAT ALL + DOWNLOAD. YOU ARE SAFE IF YOU USE DOWNLOAD ONLY.)
VIDEO GUIDES
FOR LINUX METHOD CLICK HERE - Credits to @bx2_nero
Windows Method
Requirements:
Bypass Tools Pack - (SPFLASH TOOL, DRIVER AND BYPASS FILES)
Decrypted OFP (OPPO FIRMWARE PACKAGE) Files:
FULL FIRMWARE - INCLUDES THE "USERDATA" PARTITION, HENCE LARGER.
B.53 - Mega - Google Drive - Mirror3
B.37 - Mega - Google Drive 2
B.23 (First RUI Update for the device) - Mega - Google Drive - Mirror3
A.50[EU] - Mega - Google Drive
A.42[EU] - Google Drive - Mirror2
NOU (NO USERDATA) FIRMWARE - FOR PEOPLE WITH LIMITED DATA PLAN.
B.53 - Google Drive - Mirror 2
B.37 - Google Drive - Mirror 2
B.23 - Google Drive - Mirror 2
A.50[EU] - Mega - Google Drive
A.42[EU] - Google Drive - Mirror2
Please read an explanation of what is userdata partition and how different is this from other firmware here.
Note: All files with available links above are tested.
Python (Must add to PATH during installation, see screenshot if you don't understand)
libusb-win32 - Having Issues? Use this.
{
"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"
}
Make sure to choose the last option.
1)Open command prompt by running cmd,
enter
python -m pip install pyusb pyserial json5
After the installation, you can re-run the command. If it looks like the screenshot above you're ready to go to next step.
after the installation leave CMD.
2) Go to driver folder, find the .inf file right click and press install.
3)Download this file and install it, after installing plug your phone to PC by connecting your phone to PC while doing Vol+- . You might need this driver as well if it's not detected.
Press next, connect your device to PC while holding Vol+- buttons (your device needs to be powered off) and you will see the mtkdriver down below. Install it.
Choose MediaTek USB Port and install it.
4)Turn off your phone and again connect to PC while holding Vol+- buttons then run the brom.bat under Bypass folder. If it says "Protection Disabled" in the end you're ready to go on. (If it's like the screenshot below go on.)
If you had a problem here, please check the end of the guide for it's fix.
5)Go into Flash Tool folder and open the SPFlash tool, after that choose scatter file and also if not set, set your download -agent. You don't need to select auth file as authorization is disabled. Once you do it, it should look like this. ALWAYS MAKE SURE DOWNLOAD ONLY MODE IS SELECTED! DON'T SELECT OTHER MODES!
Click choose DA Agent. (I uploaded an updated bypass tools pack, if you're using older download new one) Go into Bypass Tools Pack > Verified Boot Fix > Choose the "DA_6765_6785_6768_6873_6885_6853.bin" file.
If its giving error go into Options menu and disable option shown below. You will be able to choose a DA file.
Make SURE "Download Only" is selected. Don't select ANYTHING ELSE! You will lose your IMEIs, Serial Numbers, Capability of Hardware Attestation etc. if you choose "Format data + Download" make SURE you selected "Download Only".
After flashing it should look like this. Download has been complete. Enjoy!
Now, you can start downloading with the button and after that a checkmark will appear. You can reboot your phone and use it like before now! All your userdata will (inevitably) be cleared!
Spoiler: TROUBLESHOOTING - FAQ AND FIXES
POSSIBLE ERROR: "Verified boot enabled."
There are 2 fixes to this.
1st Method (DIRECT FIX):
Click choose DA Agent. (I uploaded an updated bypass tools pack, if you're using older download new one) Go into Bypass Tools Pack > Verified Boot Fix > Choose the "DA_6765_6785_6768_6873_6885_6853.bin" file.
If its giving error go into Options menu and disable option shown below. You will be able to choose a DA file.
2nd Method (WORKAROUND):
If you're getting this error, and you are SURE you used "Download Only" mode, there's a way to get rid of this. First, load the scatter then untick/deselect partitions listed below.
opporeserve2,
cdt_engineering,
my_custom,
special_preload,
userdata,
super,
After running brom.bat and flashing all partitions except the ones listed above, your phone will be able to reboot to stock recovery. Now select " Power Off" option then go run brom.bat, bypass authorization and then flash partitions listed below from SPFlash Tool.
super,
dtbo,
userdata
Your device will be able to boot into system after this if you have followed steps correctly.
POSSIBLE ERROR: Issues while disabling protection;
Power off your device Restart the process from 2nd step.
POSSIBLE ERROR: Issues while flashing;
Power off your device, you will need to do the bypass again. Check your USB Cable, there might be a disconnection. If not, start from 3rd step and make sure you did everything right.
Spoiler: FOR PEOPLE WHO WANT TO DOWNGRADE AND FOR PEOPLE WHO WERE ON EU VERSION
So, welcome to hell(!).
For people who want to downgrade:
If you want to downgrade to any version you would like, just use the B23 file as it is the oldest ofp file i could find for extracting process. If you were on EU version before (Any version starting with A) download ozip from here(for EU) , here(for Global) and manually flash from Realme UI recovery and format your data. Your device will be back at A.XY firmware with EU features (No heytap, no ads, no theme store, no bloatware) you had before.
For people on EU who want to unbrick:
So, you can use any version starting with B and it should work. It works in my case, i was on A.48, i flashed B53 and over that flashed B23. No probs at all. If you want to return to EU rom (starting with A) download ozip from here and manually flash from Realme UI recovery and format your data. Your device will be back at A.XY firmware with EU features (No heytap, no ads, no theme store, no bloatware) you had before.
Thanks --
https://github.com/bkerler/oppo_decrypt for decryptor.
https://github.com/MTK-bypass for creating the tool.
Thank you for your efforts. Can you add the decrypted A34 file?
mercan01 said:
Thank you for your efforts. Can you add the decrypted A34 file?
Click to expand...
Click to collapse
Hello! I wasn't able to find factory package (ofp) files for any version that makes sense for versions starting with A. (EU). There are A11 and A08 which according to update trackers, did never exist and the A.11 package is %50 larger than all the other files weirdly. I have contacted owner of some sites that do upload files like these and they asked for money. If it's a resonable price i will get it, decrypt it and upload here! If you were able to find any versions starting with A, feel free to message me on telegram (@ctivity) or email me!
Hi, it gives an error when I do unbrick with a different version, when my phone was brick the version was A34.
mercan01 said:
Hi, I have a website that publishes A24 version only. https://www.getdroidtips.com/realme-6-software-update/. It gives an error when I do unbrick with a different version, when my phone was brick the version was A34.
Click to expand...
Click to collapse
Hello again. According to the site you have just sent, A.11 is the first update to EU version. I was thinking it was a mistakenly uploaded file, since userdata partitions are for some reason 9gb with this one instead of 3. If you Downgrade to A11 using SPFLASH tool and this guide and after that install any version included here using recovery, it will work. Unfortunately, these files you sent in the link are ozip files and update packages while ofp files are firmware packages and they include everything. There are only 2 ofps -decrypted and not decrypted- available for now starting with A(EU), A08 (first ever firmware for EU) and A11(first update to EU version).
Hello again. Yes, I noticed there was an ozip file and deleted it.
daeSundae said:
If you Downgrade to A11 using SPFLASH tool and this guide and after that install any version included here using recovery, it will work.
Click to expand...
Click to collapse
First of all, thank you daeSundae for posting this info here!
Have you actually tried to flash the decrypted A.11 version? I did according to your guide. Everything went fine including the green checkmark after successful flash.
Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device.
Linux shows a device that identifies as "18d1:d001 Google Inc. Nexus 4 (fastboot)".
Fastboot does not recognize the device, adb however does, showing the correct S/N and state unauthorized, thus it doesn't accept any commands.
So the USB controller seems to be still alive, but nothing more.
To be clear: I don't blame you in any way, I'm just trying to provide information to step forward! So, what was your experience on A.11?
cmfan said:
First of all, thank you daeSundae for posting this info here!
Have you actually tried to flash the decrypted A.11 version? I did according to your guide. Everything went fine including the green checkmark after successful flash.
Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device.
Linux shows a device that identifies as "18d1:d001 Google Inc. Nexus 4 (fastboot)".
Fastboot does not recognize the device, adb however does, showing the correct S/N and state unauthorized, thus it doesn't accept any commands.
So the USB controller seems to be still alive, but nothing more.
To be clear: I don't blame you in any way, I'm just trying to provide information to step forward! So, what was your experience on A.11?
Click to expand...
Click to collapse
Hello! I'm sorry for the inconvenience I have tried flashing A11 file and it caused several problems just like in your case, however if you didn't select "Format All+ Download" mode you should be able to recover your phone. So, I had the exact same issue today and due to that I will be removing the A11 file from the links. Also, never forget to select Download Mode only! Several people bricked today and their IMEIs, Serial Numbers are all gone! Never select anything else than Download Mode!
So the solution is to download B53 decrypted files, load the scatter and untick listed partitions
opporeserve
,cdt-engineering,
mycustom,
special-preload,
userdata,
super
and then start the flashing in download mode. Now, you might be wondering "How am I going to go into the download mode again?" It's very simple. All you have to do is to keep pressing on Power and Vol- for some time and then, connecting to the pc with both volume buttons pressed while brom.bat is running. If you get an error, just reinstall device filters and that should fix the problem, then you can start downloading. After downloading these partitions to the phone, you will be able to see a boot animation and as well as a realme logo. Reboot to recovery, power of your device and then go into download mode again and flash userdata, dtbo and super partitions this time around. It should boot into system. However, the version will be B.53 but you can use the latest ozip (A.48), flash it from recovery and then format your data. It will bring you back to EU version.
cmfan said:
First of all, thank you daeSundae for posting this info here!
Have you actually tried to flash the decrypted A.11 version? I did according to your guide. Everything went fine including the green checkmark after successful flash.
Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device.
Linux shows a device that identifies as "18d1:d001 Google Inc. Nexus 4 (fastboot)".
Fastboot does not recognize the device, adb however does, showing the correct S/N and state unauthorized, thus it doesn't accept any commands.
So the USB controller seems to be still alive, but nothing more.
To be clear: I don't blame you in any way, I'm just trying to provide information to step forward! So, what was your experience on A.11?
Click to expand...
Click to collapse
So, i just read your reply again.
"Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device."
i dont think it's an issue caused by the device. Can you install oppo drivers from this link and let me know what happens afterwards? Or if you're fast enough you might prefer going into device manager by right clicking on Windows button and uninstall it's driver? I will also request you to start from step 2 to ensure installing drivers. I had the same black screen but my Windows was able to detect the Download Mode when i connected while both volume buttons pressed.
mercan01 said:
Hi, it gives an error when I do unbrick with a different version, when my phone was brick the version was A34.
Click to expand...
Click to collapse
Hello! I have uploaded B23 files both on google drive and mega. It should work for you, it is working for me at the moment. I also was on A48 firmware and both B23 and B53 versions worked without a problem.
daeSundae said:
I had the same black screen but my Windows was able to detect the Download Mode when i connected while both volume buttons pressed.
Click to expand...
Click to collapse
Well, good to hear, that your phone survived the faulty firmware. Although I select Download only of course I can't reach download mode any more. It is completely dead, Holding whatever combinations for even a minute doesn't have any effect. Normally you can force a reboot by holding Power and Vol+ for 10-15 seconds. If you keep holding it'll reboot, if you release both keys immediately after the screen went black it stays powered off. That's how I could escape the previous bootloop.
I've tried removing all devices and drivers and reinstalling them as per your guide, alas to no avail. My second, still intact phone (stock, unrooted), identifies in download mode as "USB serial device" on Windows and as "Mediatek Inc. MT6227 Phone" on Linux. The bricked always identifies as "Google Inc. Nexus 4 (fastboot)" throughout (buttons pressed or not).
It's a shame I didn't have the idea of unbricking with a B region firmware and flashing the A region later through recovery, because then I wouldn't have tried the untested A.11, but taken the verified route instead.
cmfan said:
Well, good to hear, that your phone survived the faulty firmware. Although I select Download only of course I can't reach download mode any more. It is completely dead, Holding whatever combinations for even a minute doesn't have any effect. Normally you can force a reboot by holding Power and Vol+ for 10-15 seconds. If you keep holding it'll reboot, if you release both keys immediately after the screen went black it stays powered off. That's how I could escape the previous bootloop.
I've tried removing all devices and drivers and reinstalling them as per your guide, alas to no avail. My second, still intact phone (stock, unrooted), identifies in download mode as "USB serial device" on Windows and as "Mediatek Inc. MT6227 Phone" on Linux. The bricked always identifies as "Google Inc. Nexus 4 (fastboot)" throughout (buttons pressed or not).
It's a shame I didn't have the idea of unbricking with a B region firmware and flashing the A region later through recovery, because then I wouldn't have tried the untested A.11, but taken the verified route instead.
Click to expand...
Click to collapse
Well, as far as my knowledge goes BROM is burnt onto SoC and cannot fall into an inaccessible state. You should still be able to do access download mode even if that firmware was corrupt. Do you know if your phone has any charge or not? Can you try different volume and key combinations? A broken firmware shouldn't make the BROM Download mode inaccessible.
cmfan said:
Well, good to hear, that your phone survived the faulty firmware. Although I select Download only of course I can't reach download mode any more. It is completely dead, Holding whatever combinations for even a minute doesn't have any effect. Normally you can force a reboot by holding Power and Vol+ for 10-15 seconds. If you keep holding it'll reboot, if you release both keys immediately after the screen went black it stays powered off. That's how I could escape the previous bootloop.
I've tried removing all devices and drivers and reinstalling them as per your guide, alas to no avail. My second, still intact phone (stock, unrooted), identifies in download mode as "USB serial device" on Windows and as "Mediatek Inc. MT6227 Phone" on Linux. The bricked always identifies as "Google Inc. Nexus 4 (fastboot)" throughout (buttons pressed or not).
It's a shame I didn't have the idea of unbricking with a B region firmware and flashing the A region later through recovery, because then I wouldn't have tried the untested A.11, but taken the verified route instead.
Click to expand...
Click to collapse
Oh wait. Is it identifying as fastboot? Then you should be able to (even if you don't have USB debugging authorization) use minimal ADB and fastboot tools to
use "fastboot reboot" command. Please keep pressing vol - button if you can while rebooting if it works. That should, if possible reboot you into recovery.
Also as you said, keeping pressing on power and vol+ buttons don't work in this state. In fact, in this state nothing visually works, there is no screen output and I'm actually pretty sure it's the same for begonia (RN8 PRO). You will need to ~ if it's detecting it as a fastboot device need to use minimal ADB and fastboot tools to get rid of that state. I didn't have the same issue as you though. While I was in same state, I kept on pressing on Vol - and Power buttons for around 30-40 seconds (obviously without a response from the device) and after that pressed both volume buttons and connected device to PC. Can you also try when your device powers off? Because clearly currently your device isn't powered off and cannot be powered off until the battery dies or you can somehow manage to escape from current situation.
MTK Bypass Universal
My screenshots were used in this post. I don't mind
MEGAFON929 said:
MTK Bypass Universal
My screenshots were used in this post. I don't mind
Click to expand...
Click to collapse
I'm sorry for not letting you know Dinolek. I tried to create a guide but my Windows is Single Language and since it's not global version or something I cannot change its language. I had to find an English screenshot. If it's a problem, I'll just remove them.
No, I'm not Dinolek. I just talked to him and he accepted my instructions. Let the screenshots lie, I don't mind.
Thank you daeSundae for helping me, I really appreciate that. So, what do we have:
Well, as far as my knowledge goes BROM is burnt onto SoC and cannot fall into an inaccessible state. You should still be able to do access download mode even if that firmware was corrupt.
Click to expand...
Click to collapse
Sounds reasonable and I hope it's true.
daeSundae said:
Do you know if your phone has any charge or not? Can you try different volume and key combinations?
Click to expand...
Click to collapse
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
Three buttons make 7 possible combinations. I've tried them all, pressing, holding and holding while connecting USB. No reaction at all, unfortunately.
daeSundae said:
Oh wait. Is it identifying as fastboot? Then you should be able to (even if you don't have USB debugging authorization) use minimal ADB and fastboot tools to use "fastboot reboot" command.
Click to expand...
Click to collapse
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
daeSundae said:
Can you also try when your device powers off? Because clearly currently your device isn't powered off and cannot be powered off until the battery dies or you can somehow manage to escape from current situation.
Click to expand...
Click to collapse
Sound also reasonable, however waiting for the battery to drain may last a very long time. I am out of ideas on how to force a power off otherwise (apart from sacrificing hardware integrity and disconnecting the battery of course)
Man, do I miss the old days when a ZergRush was all you needed to root and problems like this were solved by pulling the removable battery...
cmfan said:
Thank you daeSundae for helping me, I really appreciate that. So, what do we have:
Sounds reasonable and I hope it's true.
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
Three buttons make 7 possible combinations. I've tried them all, pressing, holding and holding while connecting USB. No reaction at all, unfortunately.
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
Sound also reasonable, however waiting for the battery to drain may last a very long time. I am out of ideas on how to force a power off otherwise (apart from sacrificing hardware integrity and disconnecting the battery of course)
Man, do I miss the old days when a ZergRush was all you needed to root and problems like this were solved by pulling the removable battery...
Click to expand...
Click to collapse
Can you try ADB reboot command on Linux? As it is identifying as a fastboot device?
cmfan said:
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
Click to expand...
Click to collapse
If it's detecting a fastboot device, the device isn't dead. What I'm guessing is that your device is working, and on fastboot mode but since there's no display output in this state it will only show a black screen. Can you do ADB devices command? Im guessing adb reboot requires authorization though, but it's worth trying. What I will be requesting from you is to try pressing (and keep pressing on) different key combinations while device is in that state for like a minute or so, for example keep pressing on Vol- and power for a minute then switch to Power and Vol+ for a minute and then keep pressing on both volume buttons and connect device. Can you also see the results after plugging your device into charge and letting it stay for around a minute? I know these might make no sense technically, but in my opinion randomness is your best friend to get rid of situations like this..
cmfan said:
Thank you daeSundae for helping me, I really appreciate that. So, what do we have:
Sounds reasonable and I hope it's true.
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
Three buttons make 7 possible combinations. I've tried them all, pressing, holding and holding while connecting USB. No reaction at all, unfortunately.
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
Sound also reasonable, however waiting for the battery to drain may last a very long time. I am out of ideas on how to force a power off otherwise (apart from sacrificing hardware integrity and disconnecting the battery of course)
Man, do I miss the old days when a ZergRush was all you needed to root and problems like this were solved by pulling the removable battery...
Click to expand...
Click to collapse
Hello. again. So, i have asked few people about your situation. Conclusion is, if none of these work you will need to wait until battery wears off and device turns itself off, i'm afraid. I will ask you to not use your phone for like a day and not to keep it connected to a computer for a long time. After making sure it powered off (which, i'm guessing there is actually no way to do that) make sure to prepare the brom.bat file plug in your device with VOL+ - combo and go on. Before doing this make sure to Device Manager > Action > Add Legacy Hardware > Next > Install the hardware that I manually select from a list (Advanced) > Show All Devices > Have Disk > Choose the cdc-acm.inf > Choose Mediatek USB Port and install it to not waste time. I hope your problems will be fixed. I have confirmed that BROM mode shouldn't fall into an inaccessible state because there's no efuse.ini blown. It must be there, but you're probably stuck in a mode that doesn't allow doing anything for some reason.
Has anyone had any luck rooting the new A12 P5 update yet from today? Normal method seems to brick the phone.
Easy restored it but not sure about how to approach it.
Same here. The usual method of patching and flashing the modified boot image via magisk does not work. The phone refuses to boot into system but instead boot into bootloader, saying that the boot image is not recognised / verified. Flashing the original boot image allows the phone to boot normally again so no data lost for me.
Another problem is that google pay detects root and I cannot setup in-store payment, even though I don't have root. erasing google play services and google pay data does not solve the problem.
I am going back to android 11.
fkofilee said:
Has anyone had any luck rooting the new A12 P5 update yet from today? Normal method seems to brick the phone.
Easy restored it but not sure about how to approach it.
Click to expand...
Click to collapse
Quick note. "Normal method seems to brick the phone"
Brick - refers to a device that is completely dead.
Your device was in a "bootloop".
andybones said:
Quick note. "Normal method seems to brick the phone"
Brick - refers to a device that is completely dead.
Your device was in a "bootloop".
Click to expand...
Click to collapse
Touche - Fairpoint there sir - 100 points to you!
The method we used on Android 11 will no longer work due to the introduction of Verified Boot 2.0 in Android 12.
Please read my guide on rooting Android 12
You guys should go check the new re-root thread under the Guides and news sub here.
Which the person who wrote just linked to above me.
If that still doesn't work, just use the official Android Flash Tool website, install with a wipe, and disable: verification, and dm-verity with the options provided before flashing Android 12 with this tool.
Once the update is flashed with AFT, just boot to bootloader and fastboot flash your patched Magisk image. You can do this immediately after the phone is flashed, if you're quick enough before it boots to device setup, do the key combo to get to fastboot upon boot (volume down + power), fastboot flash the patched image, then reboot.
Instant root before you even start device setup!
I just did a complete wipe and reinstall this morning, coming from Beta 5 to A12 final, and I'm rooted with Magisk, works perfect, and just like it always has.
After trying to flash TWRP (by following this guide: https://www.thecustomdroid.com/root-oneplus-6t-guide/ ) my device would no longer boot to the OS,but (stock) recovery and fastboot modes worked, so I tried to fix it by flashing some Android 9 roms from https://forum.xda-developers.com/t/...t-stock-fastboot-roms-for-oneplus-6t.3862516/ , and flashing a stock Android 10 boot.img (for some reason).
But my attemps at fixing it by flashing only made things worse, my current situation is as follows:
Device: Oneplus 6T (6/128)
Version (either Global or T-Mobile): Unsure
OxygenOS Version: Unsure, only know that it is Android 9
Bootloader: Unlocked
- Neither Recovery mode nor TWRP work
- Bootloader and Baseband versions show as empty
- I can only access Fastboot mode and EDL mode
- A power outage left my main pc (which had the drivers, permissions and backup i had been using, and need, to do this) a burning mess
- I´m currently using an old desktop computer i had stored (which has Windows 7), but it fails to recognize my device.
- I have installed and tried multiple versions of the Qualcomm, Oneplus, Adb and Android drivers, but it never recognizes it
- Windows doesnt allow me to manually select the drivers for the Unknown device as ¨the specified folder doesnt contain a software driver compatible with this device¨
- By searching the system and internet it always says that ¨the best software driver for this device is already installed¨
- Both of the above were tried with a disabled driver signature requirement
- When using it on the other PC, the msm download tool, it always said that the image didnt match the device, no matter which of the 13 versions I tried
- On my current PC, the msm download tool doesnt detect my device
I implore anyone that can provide any help or advise to do so, as I´ve already spent an entire week scouring the Internet (including the Oneplus and XDA forums) for any solution, but so far, nothing has worked. Have a good day and thank you for reading my post.
Hey man.
I'm a dude with no OnePlus 6T but have a OnePlus Nord N10. But I do know the really bad punch-in-the-gut feeling of not having a device work at all.
What does "fastboot reboot bootloader" show?? (Does your phone reboot to the bootloader upon that command being ran?)
Also did you try to flash the stock Android 9 boot.img that your device was updated to?
As for the MSM download tool, the last replies I've seen show that some people trying that on Win11 recently have got it working.
Also check if these work? https://www.thecustomdroid.com/oneplus-6-6t-unbrick-guide/
How to Unbrick Your OnePlus 6T When All Else Fails
When flashing files through TWRP, ADB, or Fastboot, there's a slight chance for things to go wrong. Whether it's user error related or something else entirely, it's always good to have a backup plan. In most cases, you'll be dealing with a semi-brick or soft-brick, which can usually be solved by...
oneplus.gadgethacks.com
Sorry if it sounds stupid but I want to try to help.
I really hope your phone gets fixed, man. Good luck!