So now that the K20 Pro subforum is open, I'd like to make a post here to quickly sum up what we have right now before any device-specific AOSP development has started.
LR.Team/wzsx150's TWRP
Original thread: http://www.miui.com/thread-24561276-1-1.html
Mirrored here: https://drive.google.com/open?id=1miIo5BZqgEHh0t5PyjwFkFryosLuFOXk
Usage: unlock BL, flash recovery image to recovery and misc.bin to misc via fastboot
Status on GSIs
PHH wiki page: https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Redmi-K20-Pro
TL;DR: the biggest issue is the pop-up camera, but that has been partially resolved by PHH (manual controls); other bugs are either generic to GSIs or not deal-breakers. I myself have been using my own LOS GSI for a week by now and I'd say it's good for daily driver, and certainly good enough as an intermediate stop before actual ROMs happen. Once the overlay I submitted is merged, all GSIs built afterwards should be on equal footing. I'll also keep eyes on the issues page in case PHH needs anything for another fix.
And finally, here's a script I made for users who want to use unencrypted storage - format /data and flash this. This one was actually made for Mix 2, but also works here, while Zackptg's universal script doesn't seem to work.
AndyYan said:
So now that the K20 Pro subforum is open, I'd like to make a post here to quickly sum up what we have right now before any device-specific AOSP development has started.
LR.Team/wzsx150's TWRP
Original thread: http://www.miui.com/thread-24561276-1-1.html
Mirrored here: https://drive.google.com/open?id=1miIo5BZqgEHh0t5PyjwFkFryosLuFOXk
Usage: unlock BL, flash recovery image to recovery and misc.bin to misc via fastboot
Status on GSIs
PHH wiki page: https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Redmi-K20-Pro
TL;DR: the biggest issue is the pop-up camera, but that has been partially resolved by PHH (manual controls); other bugs are either generic to GSIs or not deal-breakers. I myself have been using my own LOS GSI for a week by now and I'd say it's good for daily driver, and certainly good enough as an intermediate stop before actual ROMs happen. Once the overlay I submitted is merged, all GSIs built afterwards should be on equal footing. I'll also keep eyes on the issues page in case PHH needs anything for another fix.
And finally, here's a script I made for users who want to use unencrypted storage - format /data and flash this. This one was actually made for Mix 2, but also works here, while Zackptg's universal script doesn't seem to work.
Click to expand...
Click to collapse
OMG! Thank you so much in advance! ???
---------- Post added at 06:47 PM ---------- Previous post was at 06:08 PM ----------
I'd love to see a more detailed "noob friendly" guide on how I can get this twrp working on my K20 Pro. Hope one will be available in YouTube soon.
melmarPH said:
I'd love to see a more detailed "noob friendly" guide on how I can get this twrp working on my K20 Pro. Hope one will be available in YouTube soon.
Click to expand...
Click to collapse
Uhh... What difficulty do you have with simply flashing TWRP? I believe that doesn't need a guide.
Thanks for your work with PHH on getting a usable GSI image. Do you have a PD charger? I was wondering if you still get 27W charging via PD?
I'll be ordering this in the next day or 2, now the prices have come down to a sensible level on AliExpress. Hopefully by the time it arrives and I get to unlock the bootloader a few more issues will have been resolved thanks to the now released kernel sources.
Thanks a lot bro!!!!!
how do you flash the misc using fastboot? and is this english language?
narugan26 said:
how do you flash the misc using fastboot? and is this english language?
Click to expand...
Click to collapse
fastboot flash misc misc.bin
Chinese default, and you can change to English in setting via same step as other official TWRPs.
AndyYan said:
Uhh... What difficulty do you have with simply flashing TWRP? I believe that doesn't need a guide.
Click to expand...
Click to collapse
Please correct me if im wrong..
1. Unlock bootloader
2. Fastboot flash recovery twrp.img
3. Fastboot flash misc misc.bin
Is that correct?
Robbo.5000 said:
Thanks for your work with PHH on getting a usable GSI image. Do you have a PD charger? I was wondering if you still get 27W charging via PD?
Click to expand...
Click to collapse
I didn't buy the optional 27W charger; stock 18W charger charges the phone at 9V 1.85A (~17W) as measured by a physical USB meter (I don't trust any software readings).
melmarPH said:
Please correct me if im wrong..
1. Unlock bootloader
2. Fastboot flash recovery twrp.img
3. Fastboot flash misc misc.bin
Is that correct?
Click to expand...
Click to collapse
Looks good to me.
Nice to see you here @AndyYan ! Loved your consistent work on the mix2! You bought the k20pro as well?
ugene1980 said:
Nice to see you here @AndyYan ! Loved your consistent work on the mix2! You bought the k20pro as well?
Click to expand...
Click to collapse
Yeah it's my new primary device. I don't plan to do any building/"development" here though, this device should be popular enough to attract more capable devs on its own - that is, after it's released internationally.
May I ask what is the purpose of tha misc.bin?
AndyYan said:
Yeah it's my new primary device. I don't plan to do any building/"development" here though, this device should be popular enough to attract more capable devs on its own - that is, after it's released internationally.
Click to expand...
Click to collapse
Hi Andy, quick question.
Do you think the non-pro version of the phone will receive the same level of custom ROM support as the pro version? If I am not mistaking, the only difference that affects developers is the SD730 instead of the SD855. The reason I am asking is because I dislike MIUI, but (currently) only the Xiaomi Mi 9T is available where I live. I do not mind buying the non-pro version, but I do want much custom ROM support. Do you suggest waiting for the Xiaomi Mi 9T Pro or importing the Redmi K20 Pro over buying the Xiaomi Mi 9T (w.r.t. custom ROM support)?
Krullendhaar said:
Hi Andy, quick question.
Do you think the non-pro version of the phone will receive the same level of custom ROM support as the pro version? If I am not mistaking, the only difference that affects developers is the SD730 instead of the SD855. The reason I am asking is because I dislike MIUI, but (currently) only the Xiaomi Mi 9T is available where I live. I do not mind buying the non-pro version, but I do want much custom ROM support. Do you suggest waiting for the Xiaomi Mi 9T Pro or importing the Redmi K20 Pro over buying the Xiaomi Mi 9T (w.r.t. custom ROM support)?
Click to expand...
Click to collapse
Past "parallel" sub-flagships like Mi 8 SE / Mi 9 SE aren't even close to their flagship counterparts in terms of support, plus SD730 is a chip only used by 2 devices so far. Wouldn't count on it.
Still, given the two's similarity, it should be a cakewalk to get GSI running on it with the same bugs, and if something gets fixed on one, the other should benefit as well.
dmj0shu4 said:
May I ask what is the purpose of tha misc.bin?
Click to expand...
Click to collapse
idk either, but all releases for all devices from wzsx150 include this step, so I figure can't go wrong with just copying his steps.
dmj0shu4 said:
May I ask what is the purpose of tha misc.bin?
Click to expand...
Click to collapse
AndyYan said:
idk either, but all releases for all devices from wzsx150 include this step, so I figure can't go wrong with just copying his steps.
Click to expand...
Click to collapse
Configures in misc partition decides the bootloader to boot from system or recovery.
In wzsx150's flash.bat (recovery-twrp一键刷入工具.bat) , he writes 'fastboot.exe reboot' command in the end. So if we don't change settings in misc partition, the bootloader will control your phone to boot to MIUI system and recover the TWRP to xiaomi official recovery.
Other way, we can use 'fastboot boot twrp.img' command in the end, instead of flashing that misc.bin. Maybe we can use 'fastboot reboot recovery' command (I have not tested).
In summary, that misc.bin prevent phone from booting into MIUI.
If there are any mistakes, please point out.
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
AndyYan's GSI works well with few bugs.
The only 2 unsatisfactory things I have discovered are:
This GSI LineageOS don't support to unlock phone via fingerprint when screen is off, I have to press the power button first.
And this GSI only have PWM driver when screen is 31% brightness below, while the MIUI supports all brightness DC ( however, xiaomi claimed that K20Pro have HARDWARE DC screen driver ). I have tried 3rd party apk for simulate DC driver, it works, but completely ruines the optical fingerprint at low brightness due to the screen is so dim that can't lit up the finger for fingerprint camera.
Fortunately, Magisk, Edxposed, GravityBox[P] and other xposed modules work, so I will never return to MIUI.
kumoilain said:
Configures in misc partition decides the bootloader to boot from system or recovery.
In wzsx150's flash.bat (recovery-twrp一键刷入工具.bat) , he writes 'fastboot.exe reboot' command in the end. So if we don't change settings in misc partition, the bootloader will control your phone to boot to MIUI system and recover the TWRP to xiaomi official recovery.
Other way, we can use 'fastboot boot twrp.img' command in the end, instead of flashing that misc.bin. Maybe we can use 'fastboot reboot recovery' command (I have not tested).
In summary, that misc.bin prevent phone from booting into MIUI.
Click to expand...
Click to collapse
So that's why... Thanks for the explanation!
I always hold down the key combo right after flashing though, so it wouldn't boot into MIUI anyway, but good to know I don't need to do that anymore at least for this device.
kumoilain said:
Configures in misc partition decides the bootloader to boot from system or recovery.
In wzsx150's flash.bat (recovery-twrp一键刷入工具.bat) , he writes 'fastboot.exe reboot' command in the end. So if we don't change settings in misc partition, the bootloader will control your phone to boot to MIUI system and recover the TWRP to xiaomi official recovery.
Other way, we can use 'fastboot boot twrp.img' command in the end, instead of flashing that misc.bin. Maybe we can use 'fastboot reboot recovery' command (I have not tested).
In summary, that misc.bin prevent phone from booting into MIUI.
If there are any mistakes, please point out.
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
AndyYan's GSI works well with few bugs.
The only 2 unsatisfactory things I have discovered are:
This GSI LineageOS don't support to unlock phone via fingerprint when screen is off, I have to press the power button first.
And this GSI only have PWM driver when screen is 31% brightness below, while the MIUI supports all brightness DC ( however, xiaomi claimed that K20Pro have HARDWARE DC screen driver ). I have tried 3rd party apk for simulate DC driver, it works, but completely ruines the optical fingerprint at low brightness due to the screen is so dim that can't lit up the finger for fingerprint camera.
Fortunately, Magisk, Edxposed, GravityBox[P] and other xposed modules work, so I will never return to MIUI.
Click to expand...
Click to collapse
Thank you for your clarification. So for now, there is no way to not flashing misc.bin? Because i do not want to touch this partition whatsoever.
xuananh94 said:
Thank you for your clarification. So for now, there is no way to not flashing misc.bin? Because i do not want to touch this partition whatsoever.
Click to expand...
Click to collapse
kumoilain said:
Other way, we can use 'fastboot boot twrp.img' command in the end, instead of flashing that misc.bin. Maybe we can use 'fastboot reboot recovery' command (I have not tested).
Click to expand...
Click to collapse
You can use the first commad above after "fastboot flash recovery twrp.img". It should work.
I think it's ok to overwrite misc partition because configures in misc is always changed (eg. reboot to system from twrp/ reboot to twrp from system)
kumoilain said:
You can use the first commad above after "fastboot flash recovery twrp.img". It should work.
I think it's ok to overwrite misc partition because configures in misc is always changed (eg. reboot to system from twrp/ reboot to twrp from system)
Click to expand...
Click to collapse
So let me clear what I need to do, please tell me if i am wrong:
- extract the .7z file
- take the .img file (64mb) and flash it via adb normally.
- boot to recovery and install whatever i like
Related
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1......
Click to expand...
Click to collapse
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
I'm also looking for that. But if I can get TWRP on it I'd probably try SU.
How did you get to install the TWRP? I found a few posts but was apprehensive about whether I can use SPFT to flash original stock ROM if things go wrong. I suppose that would be the easiest way.
For what I paid for the phone, it's a decent enough device.
Using SD card as internal memory always result in the total capacity being reported wrongly..256GB becomes 512GB with 50% occupied, 200GB becomes 256GB with 64GB occupied. Still waiting for their tech support to reply but unlikely they would.
Cheers!
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Ibuprophen said:
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thanks for the input I will have a read.
Charlie-Boy said:
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Click to expand...
Click to collapse
Thanks for the info.
Cheers!
chooks06 said:
Thanks for the info.
Cheers!
Click to expand...
Click to collapse
No problem.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
abhijeet715 said:
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
Click to expand...
Click to collapse
Code:
https://www.needrom.com/download/twrp-armox-x/
There are other places listed on Google.
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Charlie, could share how you got the TWRP working?
Have been fiddling around until battery showed -1%.. Had to go back to stock.
Thanks mate!
Choo ks
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Follow the guide here. I did it a few times before success as I followed a guide from another site.
https://www.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
Click to expand...
Click to collapse
I think I installed magisk using this method, clearing dalvik and cache.
https://www.stupdroid.com/2018/02/magisk-16.0-download.html
Click to expand...
Click to collapse
Charlie-Boy said:
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Click to expand...
Click to collapse
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Charlie-Boy said:
Follow the guide here. I did it a few times before success as I followed a guide from another site.
I think I installed magisk using this method, clearing dalvik and cache.
Click to expand...
Click to collapse
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
You ignore the password and change the language to English from Russian. Just don't enter a password at all. The recovery won't stick as Android replaces it when you reboot. After you've completed other steps maybe OEM unlocking then it stays, or so I read somewhere.
chooks06 said:
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
Click to expand...
Click to collapse
All of them are encrypted by default now. The password in TWRP should be ignored and just change the language and select storage etc.
abhijeet715 said:
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Click to expand...
Click to collapse
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Charlie-Boy said:
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Click to expand...
Click to collapse
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
abhijeet715 said:
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
Click to expand...
Click to collapse
Mine is the same encryption is enabled. I select external SD storage and I am shown the contents using the same procedure as yourself, I cannot tell you why this is so. I am using the same technique, same phone, same settings, same TWRP, maybe we have different SD card?
That is all I can think of by way of an explanation. It works perfectly for me. I also made a backup which I can select and restore without a problem.
Hello, has anybody tried some GSI roms? Maybe the havoc os? I've heard that they should work with any Snapdragon powered device. I need to wait 6 days until my bootloader is unlocked and maybe somebody tested some roms already. Thanks in advance and stay healthy
I'm currently running phh's gsi with gcam as a daily driver ?
bigyin said:
I'm currently running phh's gsi with gcam as a daily driver ?
Click to expand...
Click to collapse
Okay nice. Are there any major bugs or do you use it as a daily driver?
Effzeh1948 said:
Okay nice. Are there any major bugs or do you use it as a daily driver?
Click to expand...
Click to collapse
For me I'm running it as a daily, there are a few bugs ie finger print scanner doesn't work but I just use pin for security anyway.
I was quite surprised how well it actually runs and very fast compared to miui, great battery etc.
bigyin said:
For me I'm running it as a daily, there are a few bugs ie finger print scanner doesn't work but I just use pin for security anyway.
I was quite surprised how well it actually runs and very fast compared to miui, great battery etc.
Click to expand...
Click to collapse
And 90hz display also works? If yes I will try it out once my bootloader is unlocked
Effzeh1948 said:
And 90hz display also works? If yes I will try it out once my bootloader is unlocked
Click to expand...
Click to collapse
No sorry just 60hz just now but tbh I've not actually missed 90hz.
There's an aosp Rom in the works at the moment for our device, so this is a good substitute until it's out for me personally.
Okay and is there anything I have to do special when I want to flash it?
bigyin said:
For me I'm running it as a daily, there are a few bugs ie finger print scanner doesn't work but I just use pin for security anyway.
I was quite surprised how well it actually runs and very fast compared to miui, great battery etc.
Click to expand...
Click to collapse
Does VoLTE work in this ROM?My SIM is Jio.
pnsdhrn said:
Does VoLTE work in this ROM?My SIM is Jio.
Click to expand...
Click to collapse
No not for me sorry.
---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------
Effzeh1948 said:
Okay and is there anything I have to do special when I want to flash it?
Click to expand...
Click to collapse
For starters you must have "stock recovery" and not twrp as it won't work.
Are you good with fastboot etc?
Effzeh1948 said:
Hello, has anybody tried some GSI roms? Maybe the havoc os? I've heard that they should work with any Snapdragon powered device. I need to wait 6 days until my bootloader is unlocked and maybe somebody tested some roms already. Thanks in advance and stay healthy
Click to expand...
Click to collapse
So I can speak to using Phh's GSI ROM as I tried out the v222 patch not too long ago. They do infact work, but they are missing a couple of features - Fingerprint does not work at all, 90Hz is not working (stuck at 60Hz) even with forcing it with ADB refresh rate command, VoLTE / Wifi Calling does not work, but the core functionality works at least. The problem I had with using the GSI, is that I bought a Xiaomi Mi 10 because it was in the premium segment of smartphones... missing all these key features with something as simple as a in-screen fingerprint or 90Hz placed it below the premium device I originally purchased. That's just my personal opinion of course, it depends how much you value your freedom over your device as the GSI/project treble images allow you to do that. There is an entry on the Phh's list for our device for what works and what doesnt. Can't link due to posting verification. Nothing has changed in terms of me testing the v222 patch.
To get to the point of fastboot if you are not experienced with debugging shell scripting, this will be incredibly tricky. Some issues are not apparent unless you see them. For example, the instructions listed on the Phh table is the following:
$ fastboot flash recovery stock-recovery.img (using official miui recovery)
$ fastboot reboot fastboot
$ fastboot flash system system-quack-arm64-ab-gapps.img
$ fastboot -w (wipe userdata)
$ fastboot reboot
I can tell you these have a LOT of caveats. For example, do you know how to enable USB debugging on your device and have the correct fastboot for your OS? If you don't, you need to know how to. Secondly, inorder to reference the "stock recovery img" file, you must point it to the directory of the image file.. if you dont know how to do any of that youre going to have a seriously tough time. Lastly, one other protip I can give you is that during the fastbootd phase, ENSURE you have fastboot connectivity by doing "fastboot devices" ! That tripped me because I had the correct drivers for ADB and fastboot, but fastbootd is another implementation after android 10. So you must have the correct drivers if you dont see your device listed under fastboot devices during fastbootd. you can grab them by googling, they come from XIaomi cn website and enabling it through Windows device manager if you use Windows. They are not signed, so you will have to bypass signature verification on bootup setting for Windows. Good luck let me know if you go through with installing it, I'd like to see how Havok performs!
xda-jimjongs said:
So I can speak to using Phh's GSI ROM as I tried out the v222 patch not too long ago. They do infact work, but they are missing a couple of features - Fingerprint does not work at all, 90Hz is not working (stuck at 60Hz) even with forcing it with ADB refresh rate command, VoLTE / Wifi Calling does not work, but the core functionality works at least. The problem I had with using the GSI, is that I bought a Xiaomi Mi 10 because it was in the premium segment of smartphones... missing all these key features with something as simple as a in-screen fingerprint or 90Hz placed it below the premium device I originally purchased. That's just my personal opinion of course, it depends how much you value your freedom over your device as the GSI/project treble images allow you to do that. There is an entry on the Phh's list for our device for what works and what doesnt. Can't link due to posting verification. Nothing has changed in terms of me testing the v222 patch.
To get to the point of fastboot if you are not experienced with debugging shell scripting, this will be incredibly tricky. Some issues are not apparent unless you see them. For example, the instructions listed on the Phh table is the following:
$ fastboot flash recovery stock-recovery.img (using official miui recovery)
$ fastboot reboot fastboot
$ fastboot flash system system-quack-arm64-ab-gapps.img
$ fastboot -w (wipe userdata)
$ fastboot reboot
I can tell you these have a LOT of caveats. For example, do you know how to enable USB debugging on your device and have the correct fastboot for your OS? If you don't, you need to know how to. Secondly, inorder to reference the "stock recovery img" file, you must point it to the directory of the image file.. if you dont know how to do any of that youre going to have a seriously tough time. Lastly, one other protip I can give you is that during the fastbootd phase, ENSURE you have fastboot connectivity by doing "fastboot devices" ! That tripped me because I had the correct drivers for ADB and fastboot, but fastbootd is another implementation after android 10. So you must have the correct drivers if you dont see your device listed under fastboot devices during fastbootd. you can grab them by googling, they come from XIaomi cn website and enabling it through Windows device manager if you use Windows. They are not signed, so you will have to bypass signature verification on bootup setting for Windows. Good luck let me know if you go through with installing it, I'd like to see how Havok performs!
Click to expand...
Click to collapse
Which android 10 rom my phone need to be in (cn or global or it does not matter?) before I can flash GSI rom. Thanks for the answer.
[email protected] said:
Which android 10 rom my phone need to be in (cn or global or it does not matter?) before I can flash GSI rom. Thanks for the answer.
Click to expand...
Click to collapse
It doesn't particularly matter because you'll be replacing the system.img and recovery.img. Ensure you dont have TWRP and you're using stock recovery. You just need an unlocked bootloader and the necessary tools. Let us know how it goes.
Bluetooth audio dont works!
xda-jimjongs said:
So I can speak to using Phh's GSI ROM as I tried out the v222 patch not too long ago. They do infact work, but they are missing a couple of features - Fingerprint does not work at all, 90Hz is not working (stuck at 60Hz) even with forcing it with ADB refresh rate command, VoLTE / Wifi Calling does not work, but the core functionality works at least. The problem I had with using the GSI, is that I bought a Xiaomi Mi 10 because it was in the premium segment of smartphones... missing all these key features with something as simple as a in-screen fingerprint or 90Hz placed it below the premium device I originally purchased. That's just my personal opinion of course, it depends how much you value your freedom over your device as the GSI/project treble images allow you to do that. There is an entry on the Phh's list for our device for what works and what doesnt. Can't link due to posting verification. Nothing has changed in terms of me testing the v222 patch.
To get to the point of fastboot if you are not experienced with debugging shell scripting, this will be incredibly tricky. Some issues are not apparent unless you see them. For example, the instructions listed on the Phh table is the following:
$ fastboot flash recovery stock-recovery.img (using official miui recovery)
$ fastboot reboot fastboot
$ fastboot flash system system-quack-arm64-ab-gapps.img
$ fastboot -w (wipe userdata)
$ fastboot reboot
I can tell you these have a LOT of caveats. For example, do you know how to enable USB debugging on your device and have the correct fastboot for your OS? If you don't, you need to know how to. Secondly, inorder to reference the "stock recovery img" file, you must point it to the directory of the image file.. if you dont know how to do any of that youre going to have a seriously tough time. Lastly, one other protip I can give you is that during the fastbootd phase, ENSURE you have fastboot connectivity by doing "fastboot devices" ! That tripped me because I had the correct drivers for ADB and fastboot, but fastbootd is another implementation after android 10. So you must have the correct drivers if you dont see your device listed under fastboot devices during fastbootd. you can grab them by googling, they come from XIaomi cn website and enabling it through Windows device manager if you use Windows. They are not signed, so you will have to bypass signature verification on bootup setting for Windows. Good luck let me know if you go through with installing it, I'd like to see how Havok performs!
Click to expand...
Click to collapse
When I try to flash something to the system partition it says that there is no system partition. All I can flash to is the super partition.
i using Phh's GSI ROM but I have a problem with the bluetooth headphones are detected but I can't hear anything
Kabanoska said:
i using Phh's GSI ROM but I have a problem with the bluetooth headphones are detected but I can't hear anything
Click to expand...
Click to collapse
Unfortunately known issue.. You can use a USB C cable but it requires an additional fix: enable "using alternate audio policy" in phh setting->qualcomm feauture Fix for Media sound-> Fixed by enable "disable audio effects" in phh setting -> misc features
Basecatcherz said:
When I try to flash something to the system partition it says that there is no system partition. All I can flash to is the super partition.
Click to expand...
Click to collapse
Ensure you are on fastbootd not regular fastboot! It will be a different logo, like yellow/orange on your phone instead of blue. That is probably causing the error, you can get there by doing the command fastboot reboot fastboot.
is there any other gsi system will run on mi 10?
Kabanoska said:
is there any other gsi system will run on mi 10?
Click to expand...
Click to collapse
Probably most of them as they're GSIs
xda-jimjongs said:
Unfortunately known issue.. You can use a USB C cable but it requires an additional fix: enable "using alternate audio policy" in phh setting->qualcomm feauture Fix for Media sound-> Fixed by enable "disable audio effects" in phh setting -> misc features
Ensure you are on fastbootd not regular fastboot! It will be a different logo, like yellow/orange on your phone instead of blue. That is probably causing the error, you can get there by doing the command fastboot reboot fastboot.
Click to expand...
Click to collapse
Fastbootd is the fastboot user space, right? I got it in LR Team TWRP but fastboot doesnt recognize it.
How to enter the right one?
Mackay53 said:
Probably most of them as they're GSIs
Click to expand...
Click to collapse
I tried more than 10 none on mi10 did not start
Credit to @user_ScoTTT
1. First of all, you need to sign up and login on the official website of Oppo in China. (Use Google Translate if you need to)
https://bbs.coloros.net/graphic?id=1498611
2. Follow the links and download the unlock program of Oppo Find x2 /x2 pro
3. Install the apk on your phone
4. Ensure your device has the latest version of your ROM installed.
5. Click "Start Applying" on the Unlock App. You will need to wait about a month. After a month, open the application, and if "Approved" is displayed, please go to the next step.
If not, Force Close the Application several times over and over, and maybe it will display "Approved".（Some Chinese citizens reported a similar situation.）If you still can't, please contact oppo online customer service, they can solve this problem for you.
6. Next, please back up your data.
7. After receiving the 'Approval' in the app.
Go to Settings - about mobile phone - version information - version number Click here five times.
Go to settings - other settings - Developer options then Check OEM unlock.
8. Once again, open the Deep Test application and click "Start the Depth Test". The phone will automatically restart and enter Bootloader mode.
9. Connect your phone to the computer.
10. Open the command prompt browse to your adb/fastboot location and enter
"fastboot flashing unlock"
then confirm. At this time, the mobile phone will give some warning information. Please read it carefully before making a decision.
If you decide, choose "unlock the bootloader" and press the power key to restart. It is worth noting that the phone will be formatted here. If you have opened "find my phone" before, you need to enter your oppo account password to start your phone.
11. You now setup your phone as normal though with an unlocked bootloader.
12. If you wish to Root then please see this guide: https://forum.xda-developers.com/find-x2-pro/how-to/magisk-root-install-unlocked-bootloader-t4157327
can i flash global rom after unlocked bootloader ?
i was wondering the same thing. i dont see why not. give it a shot and let us know. you have nothing to lose it will simply not let you flash if it doesnt work and your existing ROM/Phone will be unaffected.
Ok, so I've unlocked my Chinese Find X2 Pro using the official method, which is by using the depth testing app and waiting for approval, then unlocking via Fastboot.
But I still can't flash the global ROM using the stock ColorOS recovery. I've tried various versions, just either get the 'Installation failed' or 'The installed version is lower than current' error.
Do I need to wait until TWRP is available for the X2 Pro or is there another way? I don't want to root, just install the stock ROM from another region. Will Magisk allow me to do this?
Was really hoping unlocking the bootloader would do it, guess it's a good start
bugger.. it would appear that the ColorOS Recovery is preventing the install. So yes you would need TWRP or someone to hack the ColorOS recovery to flash without the check.
though with an unlocked bootloader you can flash TWRP as soon as it's been developed by someone.. or risk flashing a twrp from a similiar phone?
Bugger indeed, I've bricked it! Tried various ways to do it as really need to get rid of this Chinese ROM. I flashed a Boot image from a global version, didn't work. Then flashed the Chinese version back.
So then in a bold (stupid) move I tried to flash other images from the global ROM - now won't load into recovery at all. With nothing to lose I tried loading TWRP recovery from one of the latest Realme phones this morning, didn't fix it.
What is weird is in Oppo / Realme ROMs there is no recovery image - not sure if it's part of the boot image?
Does anyone know how to obtain a recovery image? I think this is what I'm missing. Thinking maybe it's not part of the ROM on these devices.
---------- Post added at 04:27 PM ---------- Previous post was at 04:22 PM ----------
And FYI, I've been using a python tool to decrypt the ozip files. Have looked in multiple ROMs, beta and standard, Chinese and global and even a few Realme ROMs.
I'm starting to hate Oppo, it's even more of a pain in the ass than Samsung! :silly:
I bought a Xiaomi Mi Mix 3 5G yesterday off eBay just to get me by for the time being, it was a carrier version and I managed to get the stock global ROM with MI12 on it in 30 minutes using fastboot and flashing all the images. Refreshingly easy
klanbo78 said:
Bugger indeed, I've bricked it! Tried various ways to do it as really need to get rid of this Chinese ROM. I flashed a Boot image from a global version, didn't work. Then flashed the Chinese version back.
So then in a bold (stupid) move I tried to flash other images from the global ROM - now won't load into recovery at all. With nothing to lose I tried loading TWRP recovery from one of the latest Realme phones this morning, didn't fix it.
What is weird is in Oppo / Realme ROMs there is no recovery image - not sure if it's part of the boot image?
Does anyone know how to obtain a recovery image? I think this is what I'm missing. Thinking maybe it's not part of the ROM on these devices.
---------- Post added at 04:27 PM ---------- Previous post was at 04:22 PM ----------
What method were you using to flash mate?
I had a look at the extract of the Global ROM and can see a heap of img files.. though your right there is no obvious Recovery image file.
That is strange. As the device has a Recovery mode. It would be very strange to make it part of the Boot Image. Surely Oppo has a recover tool that just puts everything back to default?
Click to expand...
Click to collapse
Sage said:
What method were you using to flash mate?
Click to expand...
Click to collapse
Just using the adb toools via command prompt on my PC and phone on fastboot mode.
I.e. fastboot flash boot boot.img
There's no system image either, only vbmeta_system.img which I don't think it's the same thing. Watching YouTube videos and searching the internet now to try and figure out
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
klanbo78 said:
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
Click to expand...
Click to collapse
Impressive mate well done! And thanks for posting the solution! With a recovery.img file you are now free to experiment! I hope you get the Global Working! Please keep us up to date!
Can you upload the recovery.img to help the community?
Sage said:
Impressive mate well done! And thanks for posting the solution! With a recovery.img file you are now free to experiment! I hope you get the Global Working! Please keep us up to date!
Can you upload the recovery.img to help the community?
Click to expand...
Click to collapse
You will be the first person in the world to have an unlocked bootloader on the Global ROM!
surely with some combination of Global and Chinese it will work!
Chinese Recovery -> Global Boot -> Global ROM -> Chinese Vendor
Global Recovery -> Global Boot -> Global System -> Chinese Vendor
Chinese Recovery -> Chinese Boot -> Global System -> Global Vendor
etc
etc
Sage said:
You will be the first person in the world to have an unlocked bootloader on the Global ROM!
surely with some combination of Global and Chinese it will work!
Chinese Recovery -> Global Boot -> Global ROM -> Chinese Vendor
Global Recovery -> Global Boot -> Global System -> Chinese Vendor
Chinese Recovery -> Chinese Boot -> Global System -> Global Vendor
etc
etc
Click to expand...
Click to collapse
Thanks for your support
I'll upload the recovery images for the global and Chinese variants once I'm back on my desktop later.
So the issue I'm facing now is it this phone doesn't have a system, vendor or product partition. My assumption is that I need to flash the global system image, as that's the one that basically contains the OS.
I think that these images are contained within the "super" partition which appears to be a dynamically resizable partition. I have no idea how to flash to these!
I'm trying to make sense of it all but fastbootd has come up a few times, which apparently is needed to flash to userspace which is where this super partition resides.
I can see in the ROM there is an updater script file that refers to these images, create groups in the super partition and resizes them as necessary. It seems to use the vb_meta_system image in some way. I have no idea how to replicate this script in fastboot though or if it's even possible?
Can anyone help?
---------- Post added at 08:59 AM ---------- Previous post was at 08:46 AM ----------
A bit of info on dynamic partitions...
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
vbmeta.img removes the boot verification so you definitely want to use that. see this thread for its use.
https://forum.xda-developers.com/find-x2-pro/how-to/magisk-root-install-unlocked-bootloader-t4157327
I downloaded the depth testing app but the submit application is greyed out. Any tips on what to do?
golemagg said:
I downloaded the depth testing app but the submit application is greyed out. Any tips on what to do?
Click to expand...
Click to collapse
I know they have a monthly quota, perhaps it's been reached this month.
Or maybe the servers are down? there were a few days during my application that I couldn't check the status, just assumed the server was offline - perhaps it's something like that.
Maybe just wait a few days and see.
Where is you download the app from? And do you have the Chinese variant?
klanbo78 said:
I know they have a monthly quota, perhaps it's been reached this month.
Or maybe the servers are down? there were a few days during my application that I couldn't check the status, just assumed the server was offline or something like that - perhaps it's something like that.
Maybe just wait a few days and see.
Where is you download the app from? And do you have the Chinese variant?
Click to expand...
Click to collapse
Understood. I'll keep monitoring it. Thanks a lot for the information.
klanbo78 said:
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
Click to expand...
Click to collapse
Can you please upload the recovery.img for people to use?
any other progress to report?
Sage said:
Can you please upload the recovery.img for people to use?
any other progress to report?
Click to expand...
Click to collapse
Yeah, that would be really nice. I couldn't boot also in recovery after android 11 beta:silly:
Sage said:
Can you please upload the recovery.img for people to use?
any other progress to report?
Click to expand...
Click to collapse
Here's the link to the recovery (and boot) images, have zipped them as they're quite large. I've included both variants (so PDEM30 and CPH2025).
https://drive.google.com/drive/folders/1HkNeQSuzsPDdue4KqRbDWLah0YH-CSwb?usp=sharing
In terms of progress, there is none. I got a bit adventurous and decided to flash all of the partitons on my PDEM30 with the images from the CPH2025 (manaully as there is no "flash-all.bat" file in the OTA ROM). I think it would have worked as it has for phones I've flashed this way in the past, but as I now know phones that launced with Android 10 are quite different due to having a dynamic "super" partition. This super partition contains the system, product, vendor image, etc. It should not (can't be) be flashed from fastboot as it's held in the "user space" of the phone and fastboot doesn't know how to deal with these partition types.
Pixel devices have a program called fastbootd which I think can be used for this, but Oppo doesn't appear to have that mode. Basically the phone now won't boot to recovery at all, I can only get into fastboot mode.
Not even worth holding out for TWRP as as of right now, TWRP doesn't support these dynamic partions (so any phone launced with Android 10). I contacted Oppo UK support and they said I could send in for repair, but then got told by the company who would be doing the repair (SBE UK) that they only support UK and EU devices. So looks like it might be going back to China for a repair (just need to find a freind who speaks Chinese )
Before that though I'm going to see if I can edit the recovery.img in Android Kitchen, to see if I can find the bit that's responsible for it not booting into recovery mode. I think at this point I have nothing to lose!!
I can't download unlock program of Oppo Find x2 / x2 pro, can you help me download it, thanks
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
Hello! Thx for posting this info. I have a few of questions. Can you post a simple set of instructions on how to apply this root? I have never rooted a Nubia device before but I want to root this. Will the flashing of the boot image require the bootloader unlock? Might you know if the viper4Android is working from the modules install in magisk? Thx in advance for any info you may be able to provide!
RngrYogi said:
Hello! Thx for posting this info. I have a few of questions. Can you post a simple set of instructions on how to apply this root? I have never rooted a Nubia device before but I want to root this. Will the flashing of the boot image require the bootloader unlock? Might you know if the viper4Android is working from the modules install in magisk? Thx in advance for any info you may be able to provide!
Click to expand...
Click to collapse
Also using your method would it require a user data wipe?
RngrYogi said:
Also using your method would it require a user data wipe?
Click to expand...
Click to collapse
yes, of course. it's like any standard boot loader unlocked. Which is why you do it first thing when you get the device.
Edit: I didn't see the question how to apply it -
just OEM unlock the device, and then
adb reboot bootloader
(wait for it too boot to boot loader)
fastboot flashing unlock
(accept unlocking voiding warranty, etc by pressing volume down and power)
fastboot flash boot <the boot.img>
Note that they don't recognize "fastboot boot" , which is my favorite way of rooting since it leaves the original image intact - and thus flashing is irreversible unless you get the stock OTA at a later time and flash it over. But this will not bring back the warranty and warnings.
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
greetings bro thanks for sharing the vbmeta.img file? didn't you use it?
few questions:
1. were did you find the stock firmware to pull the clean boot.img? Can you link it, I would like to have a backup if anything goes wrong
2. Is the patched boot.img for the North American Version?
So to lpedrot: Didn't need a vbmeta.
To superrama: Since it's the kernel, the CN/US/etc versions don't matter. That's handled at a much higher level of Android build, which is user mode. So same boot.img can be used anywhere (which btw is true in all cases - boot.img s only have kernel + Ramdisk anyway)
1. I found the original by looking for NX679 OTA . It was a rather large OTA payload.bin, which I used my imjtool to unpack the boot.img from. Don't have the link handy now, but I can probably dig up the payload.bin and put it in a link since I have it stored somewhere.
morpheus______ said:
So to lpedrot: Didn't need a vbmeta.
To superrama: Since it's the kernel, the CN/US/etc versions don't matter. That's handled at a much higher level of Android build, which is user mode. So same boot.img can be used anywhere (which btw is true in all cases - boot.img s only have kernel + Ramdisk anyway)
1. I found the original by looking for NX679 OTA . It was a rather large OTA payload.bin, which I used my imjtool to unpack the boot.img from. Don't have the link handy now, but I can probably dig up the payload.bin and put it in a link since I have it stored somewhere.
Click to expand...
Click to collapse
nice, thanks for the quick reply
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
On which rom you use it? Aparently its taken out from a Ianuary rom, latest being v2.32 afaik
Just whichever random firmware image I found. But you're overlooking one major thing which is - the kernel barely, if at all, changes between firmware versions . You can use this book image with any other firmware image of any date, earlier or later, and there's no reason why it wouldn't work. The Android OTA images are user mode, this is just the kernel + Ramdisk - and so are largely independent of each other. Only exception would be if there's some kernel vulnerability in that particular version of the kernel, which as far as we know now - there isn't.
Hi, thanks for the guide. I did the steps to unlock bootloader and do flash your provided boot.img.
They both worked successfully but not sure if the boot img did anything.
I have the chinese phone and I want to convert it to global. Going to the settings and choosing the local update file provided by the official website doesn't work.
Any tips?
LeonFresh said:
Hi, thanks for the guide. I did the steps to unlock bootloader and do flash your provided boot.img.
They both worked successfully but not sure if the boot img did anything.
I have the chinese phone and I want to convert it to global. Going to the settings and choosing the local update file provided by the official website doesn't work.
Any tips?
Click to expand...
Click to collapse
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
D1stRU3T0R said:
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
Click to expand...
Click to collapse
Rooting != Image locale change. To do an image locale change you need to get the device image for whichever locale you want (if you can find it) and then apply the usual Magisk method.
D1stRU3T0R said:
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
Click to expand...
Click to collapse
Hi I just joined the TG but got banned any chance of unbanning me?
User is Indiana_Gems on TG I'm looking to change my RM7 CN to global
morpheus______ said:
Rooting != Image locale change. To do an image locale change you need to get the device image for whichever locale you want (if you can find it) and then apply the usual Magisk method.
Click to expand...
Click to collapse
Thanks, I thought the two was related. I can't find any of the img files, which is why I'm stuck I guess. For older versions of the phone like Red Magic 5 they exist.
If they don't exist, is there a process to make one? Or do I have to wait
LeonFresh said:
Thanks, I thought the two was related. I can't find any of the img files, which is why I'm stuck I guess. For older versions of the phone like Red Magic 5 they exist.
If they don't exist, is there a process to make one? Or do I have to wait
Click to expand...
Click to collapse
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
morpheus______ said:
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
Click to expand...
Click to collapse
morpheus______ said:
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
Click to expand...
Click to collapse
Thanks for the details!
Is it impractical in terms of technical perspective , or is it just tedious to do? And do you think it will be released in future?
The reason I want to switch is that there are bugs mostly related to the google assistant. It resetting my settings like on default voice assistant app. It doesn't have ok google detection, sometimes doesn't open at all.
If that can be fixed maybe I can stay on CN rom, but honestly there's a lot of random bugs, it not only resets default apps for assistant but other apps too like fluid navigation gestures (FNG) app.
LeonFresh said:
Thanks for the details!
Is it impractical in terms of technical perspective , or is it just tedious to do? And do you think it will be released in future?
The reason I want to switch is that there are bugs mostly related to the google assistant. It resetting my settings like on default voice assistant app. It doesn't have ok google detection, sometimes doesn't open at all.
If that can be fixed maybe I can stay on CN rom, but honestly there's a lot of random bugs, it not only resets default apps for assistant but other apps too like fluid navigation gestures (FNG) app.
Click to expand...
Click to collapse
Hello. Have you found a solution to the problem? I also do not flash, says the version for the firmware is not suitable.
Morrovoker said:
Hello. Have you found a solution to the problem? I also do not flash, says the version for the firmware is not suitable.
Click to expand...
Click to collapse
Not yet, I guess we just have to wait
LeonFresh said:
Not yet, I guess we just have to wait
Click to expand...
Click to collapse
any news yet i wanna switch from global to cn lol
I have my bootloader unlocked.
I've downloaded the AOSP 13 Borneo Monthly Build.
I used
Code:
fastboot -w update .\aosp_borneo-img-Feb-Week4.zip
to install it. I don't have GApps now (as expected).
I've tried NUMEROUS things, but I always end up back to having to reinstall AOSP 13. And all the posts are almost 1-2 years old so outdated information. I tried to use the TWRP Android 11 based, but I of course got an error of "Cannot mount /data" despite no matter what I've done.
Is there any way to get GApps on the ASOP 13 build? I don't care about a custom rom and my phone has been wiped numerous times multiple different ways over the last our, so losing data (not that I did) isn't a problem.
EDIT: I don't mind if it's A11 or A12, A13 would be nice if possible. But I'd just like ASOP with GApps. Though I couldn't even find where the ASOP A11 and A12 builds for this phone would be (if there is any).
Try flashing BitGapps through TWRP and see if it works
traman124 said:
Try flashing BitGapps through TWRP and see if it works
Click to expand...
Click to collapse
I actually just install AOSP 13 and then flashed the Pixel Experience system image.
I've been doing this for like 8 hours of trial and error. I think what was confusing me most of the time was I didn't realize that you use fastboot in Bootloader and in fastboot. But you can only run certain fastboot commands in bootloader and only some in Fastboot mode. Which took me quite a bit to realize. Which means I would run a fastboot command in something like bootloader and it was meant for fastboot mode so it'd give me random errors that no one else got because they apparently knew the difference.
But that was confusing lol
EDIT: WELL ****E, NOW THE KEYBOARD DOESN'T WORK.
You didn't say that you wanted a PE GSI in the original post.
Also that was confusing for me the first time too (and moreso with the TCL Revvl 4)
traman124 said:
You didn't say that you wanted a PE GSI in the original post.
Also that was confusing for me the first time too (and moreso with the TCL Revvl 4)
Click to expand...
Click to collapse
Well I attempted PE GSI because there's no TWRP for AOSP 13 for this phone, the latest is A11 and that won't mount /data/
As well as the TWRP you listed doesn't work with my touchscreen and the other one avail doesn't do decryption.
There’s an SHRP build with decryption support for your phone… Would that work?
traman124 said:
There’s an SHRP build with decryption support for your phone… Would that work?
Click to expand...
Click to collapse
I've tried that myself, and decryption doesn't seem to be any better than twrp. That and it doesnt read AOSP 13 /data anyway. I've had the same problem trying to get gapps, even MagiskGapps doesn't seem to work. Is there a gapps package that can be flashed via fastboot maybe?
Not as far as I know... I’m sorry I can‘t help much further
ErraticFox said:
I actually just install AOSP 13 and then flashed the Pixel Experience system image.
I've been doing this for like 8 hours of trial and error. I think what was confusing me most of the time was I didn't realize that you use fastboot in Bootloader and in fastboot. But you can only run certain fastboot commands in bootloader and only some in Fastboot mode. Which took me quite a bit to realize. Which means I would run a fastboot command in something like bootloader and it was meant for fastboot mode so it'd give me random errors that no one else got because they apparently knew the difference.
But that was confusing lol
EDIT: WELL ****E, NOW THE KEYBOARD DOESN'T WORK.
Click to expand...
Click to collapse
Mind if I ask what you mean by "pixel experience system image"? Are you talking about the PE GSI?
Yes he means the GSI.
So. This works and you end with aosp 13 and gapps? For those of us with zero adb experience, is there a step by step on how to do this?
graewulf1 said:
So. This works and you end with aosp 13 and gapps? For those of us with zero adb experience, is there a step by step on how to do this?
Click to expand...
Click to collapse
I'm not sure how to get gapps, but you can flash aosp with fastboot update aosp.zip (replace aosp with the aosp file name). Just power off your phone, then power on while holding the volume down key to boot into the bootloader and perform this command.
LethalGamer2121 said:
I'm not sure how to get gapps, but you can flash aosp with fastboot update aosp.zip (replace aosp with the aosp file name). Just power off your phone, then power on while holding the volume down key to boot into the bootloader and perform this command.
Click to expand...
Click to collapse
right, i get that. i need to load gapps as well, i have too many paid apps there to not use it. since there is no TWRP for android 13, I need to figure out how to flash AOSP, then Gapps before the first boot.
graewulf1 said:
right, i get that. i need to load gapps as well, i have too many paid apps there to not use it. since there is no TWRP for android 13, I need to figure out how to flash AOSP, then Gapps before the first boot.
Click to expand...
Click to collapse
Well, let me know if you figure it out, cause i'm just as clueless about it as you are. I'm kind of suprised nobody's made a fastboot flashable gapps package yet.