Root Stock Android 10 (XT1955-2 RETLA) - Moto G7 Power Questions & Answers

Hey everyone,
Please pardon the nooby question. I am just confused about Android 10 and the new A/B partitions. I am currently running Android 9, fully rooted with TWRP. However, I am experiencing some slowdown and some app issues, I'd like to reset the phone and start over. I figured now would be a good time to upgrade to 10.
What is the status of root on Android 10? Is the procedure that same as previously? I just have a bit of information overload reading all the threads on here, I think it is confusing me further.
To clarify I would just like to run rooted stock Android 10.
Thanks a lot in advance, and pardon my ignorance!

To anyone who may be searching for the same information as me: My phone crashed last night so I flashed from 9 to 10, and rooted. No issues, no change in procedure.
Yes, the process is the same. Use LMSA to flash to the latest Android 10 version. Extract the boot.img of the stock ROM, and put it on the SD card of your device. Install magisk manager. Use the patch boot.img method to get a new, modified boot image. Use fastboot to flash the modified boot img, and you're in business.
More in depth instructions here.

Related

How to update my H60-L04 from Kitkat 4.4.4 Custom ROM to latest EMUI/Android

Hi everyone,
after I bought my H60-L04 about a 1,5 years ago, I unlocked/rooted my device and installed a Custom ROM (Liquidsmooth v3.2). Since that day, I didnt change anything regarding OS/ROM.
Now I want to change things up, either testing the new official update or installing a ROM thats based on a newer Android version. Using the search I saw different approaches, some people saying I need to install an old version of EMUI (2.3?) first. I don't want to brick my phone and I dont have much experience with ROMs in general. Can someone please give me a short guideline on what to do?
Thanks in advance!
- Melas
derMelas said:
Hi everyone,
after I bought my H60-L04 about a 1,5 years ago, I unlocked/rooted my device and installed a Custom ROM (Liquidsmooth v3.2). Since that day, I didnt change anything regarding OS/ROM.
Now I want to change things up, either testing the new official update or installing a ROM thats based on a newer Android version. Using the search I saw different approaches, some people saying I need to install an old version of EMUI (2.3?) first. I don't want to brick my phone and I dont have much experience with ROMs in general. Can someone please give me a short guideline on what to do?
Thanks in advance!
- Melas
Click to expand...
Click to collapse
Download the firmware you want to try (LP or MM), use huawei update extractor to extract recovery, boot, Cust and system images from UPDATE.APP (you will get it from firmware). Meanwhile make a dload folder in your SD card and copy update into it.
Flash the images to your phone using fastboot.
Fastboot Flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash Cust Cust.img
Fastboot flash system system.img
Press and hold power, vol up, vol down until the phone reboots. Let go of power but keep pressing the other two for 5,6 sec more. A forced update will start.
YOU WILL LOSE ALL YOUR DATA SO MAKE A BACKUP BEFORE DOING THIS.
derMelas said:
Hi everyone,
after I bought my H60-L04 about a 1,5 years ago, I unlocked/rooted my device and installed a Custom ROM (Liquidsmooth v3.2). Since that day, I didnt change anything regarding OS/ROM.
Now I want to change things up, either testing the new official update or installing a ROM thats based on a newer Android version. Using the search I saw different approaches, some people saying I need to install an old version of EMUI (2.3?) first. I don't want to brick my phone and I dont have much experience with ROMs in general. Can someone please give me a short guideline on what to do?
Thanks in advance!
- Melas
Click to expand...
Click to collapse
Just make sure you full unroot your device and flash stock recovery before updating. Or you will end up with a bootloop.
You may use Multitool app.
Thanks for you help, guys. My problem was that I used an old version of MultiTool and my adb-drivers didn't work.
Using your instructions I managed to install stock recovery and EMUI 4.0
derMelas said:
Thanks for you help, guys. My problem was that I used an old version of MultiTool and my adb-drivers didn't work.
Using your instructions I managed to install stock recovery and EMUI 4.0
Click to expand...
Click to collapse
No problem. It is always a good idea to factory reset after a new ROM. And wipe clean SDcard.

Really confused on steps to root / custom rom.. Help me please

I have the GM1910 version of the OnePlus 7 Pro
Ok so I had a stock OOS 10.3 on the 7 Pro I just bought used, went home and was super excited to get a custom rom installed. From my previous experience back in the day, I knew to USB Debug, OEM unlock, Advanced Reboot for convenience and followed the Havoc Custom ROm guide that said to:
1. Download the ROM, TWRP Installer, GApps, Magisk.
2. Wipe Data, Dalvik.
3. Flash the ROM, TWRP Installer (Use Unofficial Q compatible version, starting at 3.3.1.575).
4. Reboot to Recovery.
5. Flash the ROM, TWRP Installer again.
6. Reboot to Recovery.
7. Flash GApps (Optional), Magisk (Optiona).
8. Reboot and Enjoy.
Never Wipe System or Vendor partition.
After doing so, I first ran into an issue with Fastboot Mode being indefinitely stuck, but fixed that with a TWRP 3.3.1-75 version I downloaded, and was able to boot TWRP. After that, and following the guide above, I noticed it was stuck on the Havoc boot animation. I waited a good 20 minutes before realizing its likely never going to boot. I rebooted twice after that, waiting 10 more minutes each for a total of about an hour, thinking "Hey maybe it takes time". Nothing. I then tried flashing NikGapps for Android Q compatibility as latest Gapps on the OpenGapps website allows up to Android 9. I realized afterward that it was a n00b mistake so I downloaded and flashed the Beta Android 10 Beta Pico OpenGapps and Magisk Canary that also failed.
After that, I started searching around for finding a way to return to stock Android 9 to start over, thinking Android 9 had more stable support, so I downloaded and fastboot flashed the Android 9.5..11 GM21AA - Direct Download, but while showing the OnePlus stock boot animation, it freezes and then the device turns off entirely.
I'm currently waiting for the 9.5.13 Repack (taken from the Collection of Unbrick Tools thread) to finish downloading to see if I can use MSM tool to restore stock Android 9 and kind of start over. I would prefer to root / custom rom Android 9. I have no clue what I'm doing now, but honestly recall it being so easy back in the day before this A/B partition stuff and I would have considered myself to be not so much a n00b, but at least quite "experienced" but I guess thats completely irrelevant now hey!. Can someone please guide me on how I can fix this and get a custom rom booting? Thank you very much!
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
imatts said:
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
Click to expand...
Click to collapse
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
tech_head said:
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
Click to expand...
Click to collapse
I would have agreed with you yesterday, but I've used the phone for a few days and cannot stand the insanely rounded corners so I tried finding a work around. So far reducing screen height and getting rid of Oxygen OS's software rounded corners is the way to go but stock OOS doesnt give you the option, I'm hoping a custom rom will. Currently in the midst of flashing RR Android 9
Which boot slot are you trying to flash the rom on and have you tried flashing other roms? I know I've tried flashing havoc a few times and no go. I'm using blissrom right now and it works great until I get the rom I'm building and configuring and have data and messaging working lol

[Oneplus 7 Pro] Soft bricking when upgrading/rooting

Hi,
After ignoring the notification to update to Android 11 for over a month, I finally gave in an tried the update today.
I normally run stock OOS ROM with TWRP and Magisk, and updates are always fairly simple, let the OS update, overwriting the recovery and losing root, plug in to the PC and just `fastboot boot` the TWRP image, and then flash TWRP and Magisk on the phone itself, and bobs your teapot.
Alas, Android 11 shat all over those plans. With all the news out about Android 12 being in Beta, I had forgotten that Android 11 was so new to OP7Pro. Correct me if I wrong, but TWRP doesn't seem to work, which was my first mistake, but now Magisk has moved to a "need to patch the boot.img" model, which I hadn't seen before?
Anyways, after attempting to patch my own boot.img, I can no longer boot anything; phone just gets past the bootloader unlocked warning, then reboots into recovery.
I panicked then and attempted to flash one of the flashable Android 10 images from Mauronofrio's thread, which I think made things worse; now it just reboots repeatedly.
Any help appreciated, thanks!
Woops, I actually have a Oneplus 7 Pro (not a 7T). Can I move a thread myself?
I managed to use the MSM Download Tool from the last time I bricked my phone, which got me back to a bootable Android 10. Not much worse in life than losing all my data but better than a brick.
mc_teo said:
Woops, I actually have a Oneplus 7 Pro (not a 7T). Can I move a thread myself?
(...)
Click to expand...
Click to collapse
You cannot
But we gladly do this for you (as I just did)! Remember that you can always report your own posts for any type of forum maintenance you may need.
At your service and stay safe!
Timmy
Forum Moderator
A fix for your failed patched boot.img is just flashing the stock boot.img.
For upgrading (official OTA) and keep root, after installation finishes don't reboot and go to magisk, select install to the inactive slot and reboot, after reboot your phone will have the lastest update without loosing root.
And the best way to restore your phone is using msmtool

what IMG file to flash to restore OOS 12??

Installed some Pixel launcher stuff and successfully soft-bricked my 8 Pro running OOS 12, Android can still boot but runs abnormally, can boot into fastboot(d) and adb under Android works, but now I can't do things with Google play related, can't install any apk, can't connect MTP to navigate internal storage, many more symptoms to name, which I think are because of some permissions are corrupted.
Anyway I plan to resotre the OS back to normal by reflashing the same version OOS 12 OTA file, which is IN2025 C.16, however since I can't install that apk Oneplus provides to use update utility, even if I get the OTA file (and payload.bin) I cannot flash it inside Android. I guess the best bet is to flash using fastboot, and I get payload.bin on my hand, now I have a question: which IMG files do I need to flash with fastboot(d) just to restore the OS? I don't want to lose any user data, at least I don't want to see internal storage formatted as I am unable to back up the files in it, and as I see in the forum, using something like flash-all.bat or Fastboot Enhance will erase everything so they are the last options.
So to re-flash the same OOS 12 at a minimum effort and loss, is it right that I just need to flash system.img and vendor.img and that's ok? boot.img is tempered with magisk, if not necessary I prefer not to re-flash it. For vbmeta IMGs I don't know if I need them flashed, in order to flash the same system as the one already running in the phone.
Read first:
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Really read it first. Before you flash anything via fastboot.
IDK what you should do to retrive your device. But read the link above...
xtcislove said:
Read first:
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Really read it first. Before you flash anything via fastboot.
IDK what you should do to retrive your device. But read the link above...
Click to expand...
Click to collapse
Yeah I read this, and I see IMGs in the payload, that's some of the IMGs I plan not to flash until necessary

Lineage 20 back to stock

I'd like to revert to stock so I can give my phone to someone else.
I downloaded OOS 11.1.2.2 January 26, 2022 from OnePlus, then I followed these instructions. All was going well until I got to the flashing bit. Some of the files I extracted from payload.bin flashed successfully, but a bunch of them threw errors: unable to flash critical partition.
After that, I restarted my phone and wasn't terribly surprised to find a boot loop.
I researched the critical partition error and read that I need to run fastboot flashing unlock_critical, but that throws another error: device is already unlocked.
Finally, I reinstalled Lineage 20 to get my phone back to working condition.
It sounds like it should be simple to do a local update, but Lineage doesn't have that option.
Instructions to use TWRP also look easy, but I have Lineage Recovery, which doesn't have an option to flash a zip from internal storage.
A lot of people recommend these tools, but the last few pages in that thread are full of issues and make me nervous. Also, there are links for Android 8, 9 and 10, but my phone is on Android 13, and I believe the latest stock OOS is Android 11, so I'm not sure if any of these would work.
Can anyone recommend an up-to-date guide, or at least point me in the right direction?
This did the trick: https://community.oneplus.com/thread/1541327

Categories

Resources