Related
Hello guys im looking for a rooted rom my build is MHA-L29C567B190 my bootloader already unlocked and also flashed twrp or can you please help me root my stock rom thanks for your help
grodri19721 said:
Hello guys im looking for a rooted rom my build is MHA-L29C567B190 my bootloader already unlocked and also flashed twrp or can you please help me root my stock rom thanks for your help
Click to expand...
Click to collapse
Download and flash: https://forum.xda-developers.com/attachment.php?attachmentid=4302781&d=1508010356
You should now be rooted with Magisk.
Make sure you have TWRP 3.1.x from the twrp thread
ante0 said:
Download and flash: https://forum.xda-developers.com/attachment.php?attachmentid=4302781&d=1508010356
You should now be rooted with Magisk.
Make sure you have TWRP 3.1.x from the twrp thread
Click to expand...
Click to collapse
Is it really that easy? i have mine rooted with TWRP 3.1, i can flash that file and I'll have magisk? I'm on the same HW/SW version as the OP.
since the Oreo is coming out, will I need to flash stock to get the Stock Oreo update when its released? I assume so. I am new to the Mates and they seem to have a much different flash method/path than the Nexus 6p and HTC devices i have done in the past. I'm kind of leery to pursue Installing ROM's and Magisk (never used it yet) but would like to. Any tips or links to detailed instructions for the Mate flashing? I cant find, what I feel, to be detailed instructions on XDA.
thanks
sgtduckyboy said:
Is it really that easy? i have mine rooted with TWRP 3.1, i can flash that file and I'll have magisk? I'm on the same HW/SW version as the OP.
since the Oreo is coming out, will I need to flash stock to get the Stock Oreo update when its released? I assume so. I am new to the Mates and they seem to have a much different flash method/path than the Nexus 6p and HTC devices i have done in the past. I'm kind of leery to pursue Installing ROM's and Magisk (never used it yet) but would like to. Any tips or links to detailed instructions for the Mate flashing? I cant find, what I feel, to be detailed instructions on XDA.
thanks
Click to expand...
Click to collapse
If you're rooted with SuperSU or Phh you will need to restore your stock boot image before flashing Magisk,
this can be done by downloading your firmware from http://pro-teammt.ru/firmware-database/ then extacting update.app and opening it in Huawei Update Extractor where you extract BOOT.IMG.
Flash it using fastboot flash boot boot.img.
As long as you're using firmware B182+ (Loop device support) and TWRP 3.1.x you can install official Magisk/SuperSU.
Oreo will be a full firmware so it shouldn't need to verify any partition, meaning you will only need to restore stock recovery.
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!
nalin_s3 said:
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!
Click to expand...
Click to collapse
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!
Perseo99 said:
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!
Click to expand...
Click to collapse
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ??
nalin_s3 said:
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ?
Click to expand...
Click to collapse
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.
Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Can you check your pm??
There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool
jepoyxxv said:
There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool
Click to expand...
Click to collapse
I already went to 11 and flash to 3.11
But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me
jepoyxxv said:
But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me
Click to expand...
Click to collapse
If you are in 11 beta and want to downgrade..just simple flash global version and again flash 3.11 done
What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.
jepoyxxv said:
What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.
Click to expand...
Click to collapse
I just flash global from otg and tham again 3.11
walkwitmeinhel said:
I just flash global from otg and tham again 3.11
Click to expand...
Click to collapse
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.
[email protected] said:
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.
Click to expand...
Click to collapse
http://ui.nubia.cn/rom/detail/64
Oh! Didn't expect that. I just post this for Red Magic 3 device users. I don't know how RM3S actually works. Have you tried the unbrick tool from chinese version? Or just flashing the global rom from recovery is enough?
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
Let's see. Here is a link for Red Magic 3S unbrick tool. Download the non-eu ones.
If you have a Red Magic 3 with Red Magic 3s software, I will provide you the link to the other unbrick tool.
Also, you can try flashing the global rom from the stock recovery included in the package of the A11 rom that you have download.
Thanks for replying my bro.. my device is rm3s i already use rm3 and rm3s unbrick tool.. downloading fire hose programmer and image was successfully but.. my phone is still corrupted... And one thingg i dont have twrp install in my rm3s thats why its hard for me to fix it.. can you please guide or teach me how to flash stock recovery using global rom i know how to use cmd and adb
jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
So then, It's not a problem of the unbrick tool, that is actually working properly. The thing is that you didn't know how to do a correct process to migrate from cm rom to global...
The first thing you should do is reboot the phone into fastboot mode (power+vol. Down). Then, connect the phone to the PC and type the next commands in the cmd:
Code:
fastboot devices
in order to see if your device is being recognized
Code:
fastboot oem nubia_unlock NUBIA_NX629J
to unlock the bootloader
Code:
fastboot flashing unlock
in order to make your phone able to boot with a modified software. In the moment you will enter this command, you will see a screen advising you about your data (it'll be erased once you accept to unlock flashing).
After that, you can reboot your phone, that will show you an screen advising you that the bootloader is open. Accept and continue without problems.
Tell me if you have been able to make your phone boot.
Perseo99 said:
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.
Click to expand...
Click to collapse
Required in CN A10 + twrp A10, or maybe from CN A9 + twrp A9 to be able to flash
Hi All,
I have a new-to-me Oneplus 7 Pro. I have been trying to get Lineage with MicroG running. Well it has been quite the adventure and I have it to the point where I have Lineage running fine, and go to reflash TWRP and have bricked the phone, which takes a bit of time to get back to the point of having Linage running again. Specifics:
Lineage version: lineage-19.1-20221219-microG-guacamole.zip
TWRP Versions: I have found that twrp-3.6.1_11-0-guacamole.img works since my phone is at Android 11.
My questions are:
Are TWRP versions tied to Android versions?
When I am trying to get the last version of TWRP installed I have tried 2 approaches:
fastboot flash recovery
fastboot flash boot
Neither worked, phone always ends up bricked. I have used:
TWRP-3.5.1-guacamole-Nebrassy-3.img
twrp-3.6.1_11-0-guacamole.img
twrp-3.6.2_11-0-guacamole.img
I also have tried to boot the images 1st using: fastboot boot twrp-3.6.1_11-0-guacamole.img
and that bricks things.
What am I doing wrong?
Thanks
Ray
rbahr said:
Hi All,
I have a new-to-me Oneplus 7 Pro. I have been trying to get Lineage with MicroG running. Well it has been quite the adventure and I have it to the point where I have Lineage running fine, and go to reflash TWRP and have bricked the phone, which takes a bit of time to get back to the point of having Linage running again. Specifics:
Lineage version: lineage-19.1-20221219-microG-guacamole.zip
TWRP Versions: I have found that twrp-3.6.1_11-0-guacamole.img works since my phone is at Android 11.
My questions are:
Are TWRP versions tied to Android versions?
When I am trying to get the last version of TWRP installed I have tried 2 approaches:
fastboot flash recovery
fastboot flash boot
Neither worked, phone always ends up bricked. I have used:
TWRP-3.5.1-guacamole-Nebrassy-3.img
twrp-3.6.1_11-0-guacamole.img
twrp-3.6.2_11-0-guacamole.img
I also have tried to boot the images 1st using: fastboot boot twrp-3.6.1_11-0-guacamole.img
and that bricks things.
What am I doing wrong?
Thanks
Ray
Click to expand...
Click to collapse
If you look at the official installation page for your phone, you will see that Lineage OS 20 and 19.1 are supported. So you should reinstall Lineage OS 18.1 again, and then follow the steps on this page. Don't bother reinstalling GAPPS until after you upgrade it.
If for whatever reason you don't want an Android version higher than 11, let me know.
I specifically don't want GAPPS or anything remotely Google related. I had tried OS 20 and found that I had a problem installing apps - probably user error, but I don't need the latest and greatest. I am currently at Android 11.
I will read through the instructions, although the number of tutorials I have gone through is craze.
Can you tell me what the relationship between TWRP and Android version is, and are you able to sus out what I did wrong with my efforts to get TWRP loaded over the lineage 19 version I was using?
Thanks
Ray
rbahr said:
I specifically don't want GAPPS or anything remotely Google related. I had tried OS 20 and found that I had a problem installing apps - probably user error, but I don't need the latest and greatest. I am currently at Android 11.
I will read through the instructions, although the number of tutorials I have gone through is craze.
Can you tell me what the relationship between TWRP and Android version is, and are you able to sus out what I did wrong with my efforts to get TWRP loaded over the lineage 19 version I was using?
Thanks
Ray
Click to expand...
Click to collapse
rbahr said:
I have been trying to get Lineage with MicroG running
Click to expand...
Click to collapse
So I guess you don't want GAPPS, just MicroG. Definitely read through the instructions I gave you, as they are the official installation and upgrade instructions.
I would recommend installing Lineage OS 20, because it is the version that is being maintained right now.
I will attempt to guide you through the steps, but I need to know what your situation is right now: Is your bootloader unlocked? What OS do you have installed right now? What recovery are you using? etc.
I appreciate your help. Currently I am looking at a freshly updated phone with Android 11, and Oxygen 11.0.9.1.GM21AA.
The phone is a GM1917
Bootloader is unlocked and I am in developer mode. I have adb and fastboot loaded on my computer. I also have a working version of msm as I have bricked this thing 6 or 7 times...
Several times now, I have done the following:
Install TWRP
Install Lineage
Try and reflash TWRP <-- consistently fails at this point, gets stuck in a boot loop in the bootloader screen
Thanks
Ray
rbahr said:
I appreciate your help. Currently I am looking at a freshly updated phone with Android 11, and Oxygen 11.0.9.1.GM21AA.
The phone is a GM1917
Bootloader is unlocked and I am in developer mode. I have adb and fastboot loaded on my computer. I also have a working version of msm as I have bricked this thing 6 or 7 times...
Several times now, I have done the following:
Install TWRP
Install Lineage
Try and reflash TWRP <-- consistently fails at this point, gets stuck in a boot loop in the bootloader screen
Thanks
Ray
Click to expand...
Click to collapse
"Try and reflash TWRP" what do you mean, update the OS over TWRP?
I mean trying to re-install TWRP after installing Lineage
rbahr said:
I mean trying to re-install TWRP after installing Lineage
Click to expand...
Click to collapse
OK. Can you try following the installation instructions and skip the unlock bootloader step? Do so at your own risk, because the steps say you have to be on Android 12 first. If you do follow them, just make sure you follow them very carefully.
rbahr said:
I mean trying to re-install TWRP after installing Lineage
Click to expand...
Click to collapse
To my knowledge the guides that are provided on the TWRP site don't work for Android 12 and 13. From what I've heard, you have to root your phone and then install TWRP through Magisk.
Honkette1738 said:
To my knowledge the guides that are provided on the TWRP site don't work for Android 12 and 13. From what I've heard, you have to root your phone and then install TWRP through Magisk.
Click to expand...
Click to collapse
The guides I linked to point to the official Lineage OS instructions, right?
ethical_haquer said:
The guides I linked to point to the official Lineage OS instructions, right?
Click to expand...
Click to collapse
Yeah, but I was just saying how they should probably reflash TWRP instead of how TWRP's site says to, which doesn't work
Honkette1738 said:
Yeah, but I was just saying how they should probably reflash TWRP instead of how TWRP's site says to, which doesn't work
Click to expand...
Click to collapse
This build uses Lineage OS Recovery instead of TWRP.
ethical_haquer said:
This build uses Lineage OS Recovery instead of TWRP.
Click to expand...
Click to collapse
I know, but TWRP can be installed with Android 13 custom roms according to the TWRP thread.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE!!!
YOU HAVE BEEN WARNED!!!
Watch dogs is a ROM I created and it started with the OnePlus 9 Pro back in December. I have decided to bring it to the OnePlus 9, it's based on LineageOS & crDroid source & dependencies and I thank them for its use. SafetyNet and CTS passes whether your rooted or not. Modules not required. Most features are the same as crDroid but I have made some adjustments to bluetooth quality and some fonts that are not available there, plus Gapps are included.
Before you begin, if you don't have the latest platform tools installed on your windows machine. Download it here:
DO NOT FLASH GAPPS!!!! THEY ARE INCLUDED IN BUILD!!!!!
Flashing Instructions
First time installation (clean flash):
This update requires OOS 13.1 - 13.1.0.500(EX01) firmware
Backup your data
Download the ROM, and firmware flasher listed further down on this post and place all in your platform tools folder,
Extract all the contents in platform tools, Firmware flasher in folder.
You must flash firmware in bootloader.
Boot to recovery and factory reset then adb sideload
adb sideload WatchDogs-13.0-20230625-lemonade.zip
Reboot to system
reboot to recovery if you want root
adb sideload magisk.apk or adb sideload magisk.zip
Reboot to system
Update installation:
Updates can be sideloaded with custom recovery. Updates do not appear in system updater.
Sources:
ROM
Kernel
Downloads:
ROM
FIRMWARE FLASHER
Bugs?
Let me know.
Initial builds
WatchDogs-WITHGAPPS-13.0-20230312-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230312-lemonade.zip
If you require Google apps, flash the first one only!
If you do not want Google apps, flash the second one only!
You can't cross dirty flash a update which should be common sense. Example, you can't dirty flash the with gapps build then next update, dirty flash the no gapps one.
I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!
Telegram group please
lorilucille9 said:
I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!
Click to expand...
Click to collapse
That's weird. Did you try sideloading the firmware flasher first before the ROM? If you still have difficulties, I will post the dtbo, boot and vendor_boot files for you to flash to make it compatible. I don't have this phone. I have the OnePlus9 Pro so I can't test it. I'm sure it works or there would be other users saying the same thing.
I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with
lorilucille9 said:
I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with
Click to expand...
Click to collapse
Good deal, and no problem. Since I use crDroid sources, I figured that should work. I will still post the files necessary to flash recovery when I get a chance. Let me know if there are any bugs or issues with the ROM itself so I can work on it. Thank you!
I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.
incesu571 said:
I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.
Click to expand...
Click to collapse
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
thx bro
TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.
lorilucille9 said:
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.
Click to expand...
Click to collapse
correct, sorry, forgot to mention that as well. Thank you!! crDroid doesn't offer a with gapps build. You can use the no gapps build to flash your own gapps but I won't support force close issues with the ROM. Example, pixel setup wizard can't be used because it interfers with the default launcher. And yes, on updates, just sideload the with gapps build and your done, unless you want root, then you will have to reboot and sideload magisk because root will be gone on a update.
incesu571 said:
Telegram group please
Click to expand...
Click to collapse
There is one in my 9 pro thread. I will update when I can.
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
Convert your T-Mobile to EU as listed on another thread, then you can use the EU firmware. I will be posting a update soon with the boot, vendor_boot and dtbo. If you don't want to do that, I will post them later to flash recovery on your phone. Keep in mind that different variants act different, so you may have bugs on T-Mobile, it wasn't tested.
screenshots?
pubmastervnt said:
screenshots?
Click to expand...
Click to collapse
Not by me, maybe someone else who is running it
MARCH UPDATES: 03/24:
WatchDogs-WITHGAPPS-13.0-20230324-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230324-lemonade.zip
Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
You can use my custom recovery, files added in OP. You still need latest stock A13.
fastboot flash --slot all boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
You cant install this (or any rom but base 11) on tmobile 2117 without BL unlock key. Pretty sure its not possible.
You can only convert to base global 11\OOS11 on 2117 for root, then in ui updater doesnt work OTA or manually. You can get to 13 stock only, because you need to be stock to ota, where you need a key to unlock bootloader again (conversion would bring you back to 11).
*The rooting situation with this phone sucks. I think Jaguar is the only one that will work because it is base 11.
Hi! Are there any pro’s out there that can help out with some issues, we are having with 3 phones.
It would be greatly appreciated. I believe we are not the only ones.
How can a BOOT.IMG be extracted from an Android Phone if there is no Stock Firmware ROM available?
All 3 phones manufactured in 2022.
The Bootloader is unlocked for all 3. USB Debugging is turned on.
- Moxee m2160 MH-T6000 only boots to Fastboot & Recovery. I have tried to restore but it will not restore.
- Vortex V22 has a GSI Pixel Experience Plus 13 ROM installed and is unable to go back to factory ROM image.
- ANS ACK2326 is on a stock Android 12 ROM and hasn’t been modified but has a build number kirk2_v1 2.0_BTM-ST.
Is it possible to get a Generic BOOT.IMG to modify for root?
Are there other ROMS like GSI’s with a BOOT.IMG that could work to try to get root?
Are there other ways to get root without a BOOT.IMG?
Is there a way to parse the entire phone to compile a BOOT.IMG?
The manufacturers were contacted. No system firmware ROM is available online that we could find after searching. We don’t have any experience searching china websites or know where to begin. If someone knows where we could find the stock ROM's on a China website that would be a great help!
Are we SOL? Are phones that don’t publish stock firmware that secure that if you need a BOOT.img from stock firmware to get to access the entire encrypted rom, you are out of luck?
Or, would we need a Jtag hardware reader?
Thank you in advance for your time and help which is greatly appreciated!
The boot image contains the kernel for that specific device; there is no such thing as a "generic boot image", as the kernel has to have the basic drivers for that specific device's hardware.
It's possible to dump the boot image if you already have root, but I'm assuming that the whole reason you want the boot image is to patch it with Magisk to gain root.
The alternative, if TWRP is available, is to use ADB through TWRP to dump the boot partition.
If you can't use TWRP and aren't rooted, there is no way to dump the boot partition through fastboot.
V0latyle said:
The boot image contains the kernel for that specific device; there is no such thing as a "generic boot image", as the kernel has to have the basic drivers for that specific device's hardware.
It's possible to dump the boot image if you already have root, but I'm assuming that the whole reason you want the boot image is to patch it with Magisk to gain root.
The alternative, if TWRP is available, is to use ADB through TWRP to dump the boot partition.
If you can't use TWRP and aren't rooted, there is no way to dump the boot partition through fastboot.
Click to expand...
Click to collapse
Thanks you for the reply! That is correct. Our ultimate goal is to gain root on these devices. Is Magisk the only root pathway or are there other rooting options?
Can you use ADB Shell, ADB root and dd to pull the boot partitions?
There is not a TWRP available for these devices. How would you go about making a TWRP for these phones? Do you need the stock firmware?
defcondoc said:
Thanks you for the reply! That is correct. Our ultimate goal is to gain root on these devices. Is Magisk the only root pathway or are there other rooting options?
Click to expand...
Click to collapse
No, but it is the most popular and arguably the best
defcondoc said:
Can you use ADB Shell, ADB root and dd to pull the boot partitions?
Click to expand...
Click to collapse
No, because again you need root to run adbd as root. I could be wrong...
defcondoc said:
There is not a TWRP available for these devices. How would you go about making a TWRP for these phones? Do you need the stock firmware?
Click to expand...
Click to collapse
I am not a developer so I have no idea but I imagine you'd need the original kernel source, yes.
If u have mtk there are many options
1:using mtk client
2: using mtk bypass and wwr2
Then if u have snapdragon u need the gfil software and the phone firehose programmer
another risky way is to flash rooted GSI. but in case it boot loops, you are screwed without stock ROM. the user @gregeerg ended up with a semi bricked phone, luckily he was able to pull boot.img from adb, so another member @Jet! with same device could finally root his phone and provide super.img for unbrick. So this method is only working if you have two identical phones.
kelvinchinedu said:
If u have mtk there are many options
1:using mtk client
2: using mtk bypass and wwr2
Then if u have snapdragon u need the gfil software and the phone firehose programmer
Click to expand...
Click to collapse
I actually had or was going to ask this if there is a way to access firmware from the hardware level. Somehow the post never got posted or deleted.
Anyway, with MTK Client & QFIL, how complicated is it to extract the firmware from a device? Will it work with all devices, or will I run into issues with newer devices? I will do some researching on these and see what I can find. Thank you!
alecxs said:
another risky way is to flash rooted GSI. but in case it boot loops, you are screwed without stock ROM. the user @gregeerg ended up with a semi bricked phone, luckily he was able to pull boot.img from adb, so another member @Jet! with same device could finally root his phone and provide super.img for unbrick. So this method is only working if you have two identical phones.
Click to expand...
Click to collapse
Interesting. Where can I get a rooted GSI? I tried to searching but couldn't find anything. Is there a special way to search for one. I would be willing to try this. I had a boot loop on one and a unofficial unrooted PixelExp13 GSi fixed it.
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
alecxs said:
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you! I'm assuming these are all GSI builds from LOS 16-20? Am I also correct in saying the difference in the bgN, bvN, bvS, files? b = a/b system, g = gapps installed, v = vanilla - no gapps installed. N = No Root? S = Root?
To get a GSI that is already rooted, I must install the file with S in the filename?
alecxs said:
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Click to expand...
Click to collapse
OMG Thank you alecxs! Bravo! This is exactly what I was looking for! One install with no stock ROM rooted successfully!, two more to go. And especially thanks to andyyan for making this GSI image possible!
defcondoc said:
OMG Thank you alecxs! Bravo! This is exactly what I was looking for! One install with no stock ROM rooted successfully!, two more to go. And especially thanks to andyyan for making this GSI image possible!
Click to expand...
Click to collapse
May I ask you which of your devices listed above did you get it to work on the reason I ask is I have 2 of those phones am I'm trying to do the same thing. Thanks
omb714.1980 said:
May I ask you which of your devices listed above did you get it to work on the reason I ask is I have 2 of those phones am I'm trying to do the same thing. Thanks
Click to expand...
Click to collapse
The Vortex V22 I got to work successfully with a GSI root. I was able to get root with the Moxee but I have yet to get a custom rom or working GSI rom. I'll post when I get a working rom with the Moxee. The ANS has been a bit of trouble because I cannot get the BL unlocked even though it has OEM unlocking turned on.
defcondoc said:
The Vortex V22 I got to work successfully with a GSI root. I was able to get root with the Moxee but I have yet to get a custom rom or working GSI rom. I'll post when I get a working rom with the Moxee. The ANS has been a bit of trouble because I cannot get the BL unlocked even though it has OEM unlocking turned on.
Click to expand...
Click to collapse
I'm having the same issue with the ANS your not alone.
omb714.1980 said:
I'm having the same issue with the ANS your not alone.
Click to expand...
Click to collapse
I appreciate you letting me know. Good to know I'm not the only one.
Did anyone ever figure out how to unlock the bootloader yet?
ronnieshane1 said:
Did anyone ever figure out how to unlock the bootloader yet?
Click to expand...
Click to collapse
I do know it is available somewhere and most likely password protected but to my knowledge it hasn't been made publicly yet. I'm still waiting as well. I've be able to do some workarounds with the stock rom but I would really like to get access to the firmware or boot image.
defcondoc said:
I do know it is available somewhere and most likely password protected but to my knowledge it hasn't been made publicly yet. I'm still waiting as well. I've be able to do some workarounds with the stock rom but I would really like to get access to the firmware or boot image.
Click to expand...
Click to collapse
I know right! I cant find hardly anything on the ACK2326 at all! I wish they would go ahead and make it public already.