Hi all, I recently got this phone, the M700AR specifically, and I'm now getting to the conclusion that I can not root or install twrp or nothing... Thing is, I can't enter fastboot mode with adb, it will just reboot normally. Lg has a tool for unlocking suck bootloaders, but my model doesn't apply, and even if it did, you have to fastboot oem check the system id of the device with fast boot which I just can't boot into. I wonder if anyone is in similar poistion or can point me in the right direction, im starting to wonder if i could use the LG UP tool and LG Firmware Extractor to flash a somehow customized kdz with a specific recovery , dont know if that would do it, any how , i would like to know which kind of "lock" is this or how it works, and if its just the recovery partition and is flashable because, in download mode you can theoretically flash all partitions, thats what a kdz is about right?Any input is gratefully appreciated.
Did you find the solution?
I think it may be possible, but I've never seen it done before especially on a locked bootloader such as our LG Q6 phones. I'm not completely sure about this but locked bootloaders are mandatory to check system integrity on boot, so if we extract a KDZ file and modify the files and flash a Q6 with our modified KDZ, it won't allow for a boot and force us to flash stock ROM. Although it would be cool to see someone try it, maybe I could try it by modifying a file slightly (I don't know how to make a custom rom or KDZ) and flash it and see if it triggers system integrity check to fail. However I only own this one device and I wouldn't want to brick it (although it should be possible to boot into download mode and flash stock ROM and everything would be back to normal, unless download mode is flashed as well in a download mode flash, maybe someone could correct me here) as it would probably void warranty. Just wish LG make it simple and give us bootloader unlock, it would be grateful :^)
Related
I have been rooting for about a year now, albeit largely with Samsung devices via Odin and CWM Recovery. I now have a Verizon Motorola RAZR HD (xt925) and have been unsuccessful with unlocking the bootloader. I decided to use Safestrap with it, and tried to load Eclipse-v5.0-build2-xt926, reportedly compatible with my XT925... now i am stuck with this screen:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-02-14 09:13:08)
eMMC Info: Size 16GB
Deviced is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have been looking to XDA for my answers over the last year. Help would be appreciated. Twenty-five dollars worth of appreciation.
(Yes, I have resorted to bribes....)
Easy fix,
download what ever version of the system software you had on it previously.
Flash it in fast boot mode.
?????
Profit.
Edit: also Verizon RAZRs are xt926 not xt925
Darbness said:
Easy fix,
download what ever version of the system software you had on it previously.
Flash it in fast boot mode.
?????
Profit.
Edit: also Verizon RAZRs are xt926 not xt925
Click to expand...
Click to collapse
Phone identified itself as 925... either way, i am unsure where i can find stock software for it and seem to be unable to flash anything from fastboot, because as it turns out, i am code-retarded. definitely profit when this is solved. I can "cd" through dos and get to where fastboot commands are entered and I have even tried to "fastboot recovery recovery.img" but for the life of me, i must be typing the string incorrectly somehow. But I am excellent at following clear-cut directions. i will try to find a stock image...for motorola, it is a .sbf file, right? If i seem stupid, i apologize, i'm not. just not up on all the nomenclature native to adb and fastboot (or linux). Thanks for helping me though.....i need it.
Ok,
First thing I want you to do is look on the back of the phone, It will have the model on the lower half of it.
Second thing is to find the official software.
For XT96:
http://sbf.droid-developers.org/vanquish/list.php
For xt925
http://sbf.droid-developers.org/vanquish_u/list.php
Flash the ROM file using RSD Lite.
If it dosnt work:
Make sure you have the moto drivers installed.
open up the .xml file in the rom and remove the "getvar" lines.
Still trying
Failed at 16/27 flash system system.img
What version did you try?
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-4_VQW_CFC.xml
having a hard time finding other .xml files to use... any non-stock .xml available? really want to get into an AOKP/CM/PAC/Liquidsmooth/Carbon/Paranoid.....whatever is 4.2.2
No, only official roms are packaged like that.
You need to have RSDlite at least Version 6 or higher. Also, edit the xml file as stated here.
If your phone is up & running again you can consider going to another rom either with safestrap or by unlocking your BL, installing a recovery and flashing any ROM you like. As stated above you can only flash Stock FW using RSDLite. All other roms can only be applied with either safestrap or CWM Recovery (or similiar).
HELP-ME
FRIENDS, AFTER I TRY TO INSTALL A ROOM 4.2.2 MY PHONE NO OUT OF AP fastboot.
JA TRIED TO PUT ALL ROOMS OF MOTOROLA BUT NOT RESOLVED.
SCREEN IS BLACK AND PHONE DOES NOT NOTHING COULD HELP ME?: (
There is only 1 main point that I wanted to share with others....
DO NOT EVER EVER TRY TO FLASH THE BOOTLOADER OF ANY ROM OTHER THAN 5.0/5.0.1 OR LATER VERSIONS AFTER YOU HAVE UPGRADED TO LOLLIPOP!!.
Let me tell you first what happen if you do so........
1.) 95% Probability of Permanent Hardbrick Device
2.)Intense Graphical Glitches[These can be get rid off by flashing cm12 or any Android OS 5.0/5.0+ since it has upgraded bootloader]
3.)You May NEVER ever recover your device again.
How will you recognize you are about to flash Bootloader??
It usually has a name "motoboot.img"
What if the name is different?!
Let this time the name is abcdefg.img
The guide you may be following will ask you to perform a command line query on fastboot by the syntax-
"fastboot flash motoboot "abcdefg.img"
Pay attention it still has motoboot in command line.
Now why this happens??
I believe that with the release of Android 5.0 aka Lollipop, the Bootloader of ROM has been upgraded and modified to work with ART system efficiently.
So if you flash the older Bootloader over an upgraded one, you are gonna regret your move completely.
What is Permanent Hardbrick?!
This is a state of your phone which cannot be recovered either easily or permanently. Your device becomes completely useless. You will only see a black screen. Neither you will access Fastboot Mode nor Recovery. Your Phone will become a showcase or in other words a real BRICK.
An Advice- If you are going to flash a zip via a custom recovery like TWRP/CWM/PHILZ. First do check it by opening that it should not have the bootloader image file. If it has, make sure you delete it and then try flashing it.
Now I will share my experience-
How I Downgraded successfully
1.) I Installed a custom recovery via fastboot. [TWRP 2.7.1][2.8.1 WILL DO IT TOO]
2.)Wipe Data/cache/Dalvik Cache/etc,..The normal procedure.
3.)Copied the ZIP file of Moto G Revolution G XT1033 4.4.2 Brazil Firmware to my pendrive.
4.)Make sure your pendrive is in FAT32 Format. if not do a format in FAT32.
5.)Connected via OTG Cable to my phone in recovery mode to TWRP Recovery.
6.)Mount OTG Storage in Mount Option.
7.)Chosen my zip file under flash option and flashed it successfully.
Cons: A water like wave keeps coming from the top of the screen to bottom while booting up but goes off as soon as you turn your screen off for the 1st time. then its all normal again.
Link to Revolution G Firmware- https://forum.xda-developers.com/showthread.php?t=2690047
Guys this is my 1st post here that is well laid. Hope you thank me if this helped you.
There's a tool called Motoflasher. It can do a blank-flash your corrupted bootloader with the latest one. But until today it only support 4.3, 4.4.2, 4.4.4. And for 5.0 will be coming soon. Motoflasher is a tool to revive your-corrupted-bootloader-device after do an accidental downgrade. :fingers-crossed:
Yes, but I want to know, what would happen, when you delete the bootloader. Will it still be under device manager. So will it get detected by windows?
Why would someone do that?!
Freakfussel said:
Yes, but I want to know, what would happen, when you delete the bootloader. Will it still be under device manager. So will it get detected by windows?
Click to expand...
Click to collapse
Delete the actual bootloader from the phone?! I would not recommend you to do that. Coz bootloader is the final option for a device's recovery.
Got a G3 with no download mode.
If you Google it, it's a common issue, and the fix seems easy.
But fastboot won't communicate with the phone at all. Device shows as ? in fastboot instead of normal device ID. And can't fastboot flash, fastboot erase, or fastboot boot any imgs - get a FAIL every time.
Anyone seen this before...?
I have been through this situation (and worse). Unfortunately, I do not see a simpler way for you to get back the partitions you have messed up. If it's only the download mode you've lost and you can boot up to put the phone in adb mode, and have the root access, problem can be solved by flashing a dump of appropriate partition(s). If not, then pushing a bootloader through octopus box is the only solution for d850 as other diagnostic tools to repair the bootloader do not have appropriate files for this model. Have a look at this thread, and see if you can make any sense out of it. I am here if you need further help in this matter.
unikorn74 said:
I have been through this situation (and worse). Unfortunately, I do not see a simpler way for you to get back the partitions you have messed up. If it's only the download mode you've lost and you can boot up to put the phone in adb mode, and have the root access, problem can be solved by flashing a dump of appropriate partition(s). If not, then pushing a bootloader through octopus box is the only solution for d850 as other diagnostic tools to repair the bootloader do not have appropriate files for this model. Have a look at this thread, and see if you can make any sense out of it. I am here if you need further help in this matter.
Click to expand...
Click to collapse
No it was completely hosed - wouldn't boot and was attempting to flash laf in order to get Download Mode back. You're referring to the JTAG service via Octopus, correct?
iBowToAndroid said:
No it was completely hosed - wouldn't boot and was attempting to flash laf in order to get Download Mode back. You're referring to the JTAG service via Octopus, correct?
Click to expand...
Click to collapse
Yes, that's how I got my phone fixed. Could not find any other way, and even with this one, it was not so straight forward. Especially when working with partitions dump. I overwrote EFS partitions as well, so lost my IMEI. But if you choose to go with this method, I can guide how to just stop at recovery partition and not overwrite modemst1 & modemst2 partitions. First task though would be to find someone with Octopus Box.
I tried to root my phone and install TWRP via the tungkick method, but I forgot to do the ADB fastboot oem unlock before I flashed the modified TOT file, so when I tried to boot into TWRP it got stuck in a bootloop.
Ive downloaded the stock 10D files, but am having issues getting the phone into DL mode so I can reflash the stock files via LGUP. Ive looked though many XDA threads, and have seen a few people post the same issue, but I have yet to find a solution to my issue. Can anyone offer up some assistance?
FluXX66 said:
I tried to root my phone and install TWRP via the tungkick method, but I forgot to do the ADB fastboot oem unlock before I flashed the modified TOT file, so when I tried to boot into TWRP it got stuck in a bootloop.
Ive downloaded the stock 10D files, but am having issues getting the phone into DL mode so I can reflash the stock files via LGUP. Ive looked though many XDA threads, and have seen a few people post the same issue, but I have yet to find a solution to my issue. Can anyone offer up some assistance?
Click to expand...
Click to collapse
To get to download mode try removing battery for a couple seconds, putting it back in and then press and hold volume up while plugging in the USB cable to the computer. Also, you may want to download the 20A kdz and use the recowvery method instead of using the 10D tot file (unless you're wanting to stay on MM for some reason).
Remove battery, insert again. Hold Volume- and connect phone to PC via cable. It will take you to fastboot mode. Write command (make sure drivers & minimal fastboot and adb is installed)
fastboot oem unlock
fastboot reboot
phone will boot to system if everything is fine.
The end goal for the root process is to install TWRP and then CM or a variant of CM. I hate stock software.
Follow this guide to flash 20a firmware then
Follow this guide for rooting+twrp and you are good to flash any custom rom built for this
FluXX66 said:
The end goal for the root process is to install TWRP and then CM or a variant of CM. I hate stock software.
Click to expand...
Click to collapse
If you're wanting something customizable, fast and stable, I'd check out Resurrection Remix after following those guides listed to get 20A, root and TWRP. You may also want to check the dual boot thread and use that to try multiple ROMs at a time and see what you like the best
Disclaimers:
> I am NOT encouraging anyone to do this. I'm not responsible for anything that happens to your device once you've rooted it already. I did this out of curiosity and I'm just sharing my experience.
> Also yeah, Rmx2040. Not Rmx2040EU.
> It's doable, but it is NOT stable. It boots but you can't use the phone normally. You know, like how you'd normally use a phone.
> I SOFTBRICKED MY PHONE.
Bugs:
UI Restarts every time you go landscape and go back to portrait
Can't open camera
UI Restarts every time you scroll on playstore or anywhere with lots of images
Phone lags, actually no, it restarts all the damn time
NOTES:
@Kraitos was looking for boot.img files so i decided to do a little digging too. I saw in a post somewhere that you need vbmeta.img and a patched (via magisk) boot.img from the device itself.
The "vbmeta.img" I used here was from a Realme 5. I figured all they 'kinda' looked the same plus I don't know if the file is also patched. I tried patching it in magisk but it didn't work, so I just grabbed a (patched?) vbmeta.img (from Realme 5 somewhere in the internet) and used that for our device which is, Rmx2040 (6i)
I grabbed the boot.img from the official ozip file in realme's site (From version A.27, I couldn't find any boot.img for A.31 because they haven't updated the link in the site yet). I opened it up, looked for it, grabbed it and patched it using magisk. Thankfully, it worked.
I used both the vbmeta.img (again, idk if it's patched) and the patched boot.img to root my device. I doubted it too, I thought it'll give me a bootloop or something, but it didn't.
If you want to do it, here are the steps:
Unlock your bootloader. Go here:
https://forum.xda-developers.com/realme-6i/how-to/unlocking-bootloader-realme-6i-rmx-2040-t4174255
Credits to @Kraitos for this awesome guide on how to unlock Rmx2040's bootloader.
If you're done unlocking your bootloader, download these files:
boot.img:
https://drive.google.com/file/d/1D7S9JGwDusyL6hJ6pWrFRBLo_9DdQLGR/view?usp=sharing
vbmeta.img:
https://drive.google.com/file/d/1Do2SfGI_Tp2jERcO77Vh1vEfjiQ6Xxe9/view?usp=sharing
Portable adb fastboot (if you don't have it yet):
https://drive.google.com/file/d/1m78UIsabMQlCvNIIv2e4xI19pN9b1otw/view?usp=sharing
Put all in one folder, it doesn't have to have a name.
Extract the zip file (minimal_adb_fastboot_1.4.3_portable.zip)
*Your folders should have the ff:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
boot.img
cmd-here.exe
Disclaimer.txt
fastboot.exe
vbmeta.img
Enable USB debugging in your phone.
Connect your phone to your pc.
Double click "cmd-here.exe"
Type the following in CMD:
adb reboot bootloader
If it displays a text in the middle, type "fastboot devices" on cmd. You SHOULD your phone's code there. If it doesn't display anything, replug the type C cable on your phone and type it again, do this until it shows.
Copy this and paste it in CMD:
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Then press enter.
once it's done, copy this next:
fastboot flash boot boot.img
Then press enter.
Reboot your device by typing this in CMD:
fastboot reboot
If you've made it this far, you should install the latest Magisk Manager after you've unlocked the bootloader though. Or do it last, whatever you prefer works.
Viola, now you have an unstable phone.
I'm gonna try locking my bootloader later to flash the A.27 ozip later, I hope going back to "stock and unrooted" fixes the bugs I've experienced :|
I don't really know anything besides trying stuff out, I just wanted to see if it'll work properly with root. If anyone here noticed that I've done something wrong, please do tell me. I wanna try all the methods we can think of just so we can root this device.
Have a wonderful day y'all
Edit:
Everything went bad. I locked the bootloader because I needed access to stock recovery. It gave me a "red state"
I don't know how to fix this problem :|
Awesome guide and thanks for mention you know some people do that if you pay them to unlock bootloader and rooting device so this thread will be a savior to alot of people , I'll do testing in a couple of days asap i get a laptop relocking bootloader is mostly the same when you unlocked bootloader so it should be easy to flash stock again
Alright, so, quick update:
I tried to lock the bootloader while it had root (in my case, magisk). When I did, the phone went to "red state" (For those who don't know, it's basically bootloop wherein the phone never goes to recovery no matter what you do. Not even in stock).
Now, my phone is broken. It bootloops. I don't know what to do with this problem except going to a service center and have this fixed. Does anyone know how much it costs for reflashing stock rom to realme devices?
Sidenote: I tried the volume + down/up method to get into fastboot mode or stock recovery, but it never works. And honestly speaking, I don't think it will. To get into fastboot mode the bootloader needs to be unlocked, so that's crossed out AND I can't get into stock recovery because the phone restarts every 5 seconds because of that pesky "red state" thingy at the start.
Joesh.lucas said:
Alright, so, quick update:
I tried to lock the bootloader while it had root (in my case, magisk). When I did, the phone went to "red state" (For those who don't know, it's basically bootloop wherein the phone never goes to recovery no matter what you do. Not even in stock).
Now, my phone is broken. It bootloops. I don't know what to do with this problem except going to a service center and have this fixed. Does anyone know how much it costs for reflashing stock rom to realme devices?
Sidenote: I tried the volume + down/up method to get into fastboot mode or stock recovery, but it never works. And honestly speaking, I don't think it will. To get into fastboot mode the bootloader needs to be unlocked, so that's crossed out AND I can't get into stock recovery because the phone restarts every 5 seconds because of that pesky "red state" thingy at the start.
Click to expand...
Click to collapse
The problems you faced after rooting the phone is because you flashed an older version of boot.img thats why it wasn't working with latest rom and caused instability in system... And the second problem that you faced that red state thing..!! it was your fault you shouldn't relocked the bootloader with a patched boot img.. and if you wanted to boot the stock recovery you should have used the command " fastboot reboot recovery " this command in fastboot mode reboots the phone to recovery mode... Well i want to know what happend did your phone survived??
mehdi.shah said:
The problems you faced after rooting the phone is because you flashed an older version of boot.img thats why it wasn't working with latest rom and caused instability in system... And the second problem that you faced that red state thing..!! it was your fault you shouldn't relocked the bootloader with a patched boot img.. and if you wanted to boot the stock recovery you should have used the command " fastboot reboot recovery " this command in fastboot mode reboots the phone to recovery mode... Well i want to know what happend did your phone survived??
Click to expand...
Click to collapse
Thanks for the information, I now understand that I should use the same boot.img. It was worth the experiment tho, I just hoped I did it better so I wouldn't have to go through this process again.
My phone is here with me. It's still stuck on red state and I haven't went to a service center to have it fixed yet. I went to Hovatek to look for some ways to fix this problem. I tried using miracle box and the SP flashtool method but the latter had problems with the scatter file and the former didn't get past this:
Waiting for USB Port...
Set OPPO PreLoader USB VCOM (Android) (COM4)
>>Please Hold "ON" to connect with the phone...
I also looked a little bit more into it and I found out that I can use the OFP file and the flasher application here: https://firmwarex.net/realme-6i-rmx2040-official-firmware/
But unfortunately, I can't use the application because it's asking for an OPPO ID or something. Either I bring this phone to a service center or I'll just let it be this way until I decide to sell it somewhere. I hope I'll be able to fix this on my own tho, at least, someday.
Edit:
You can read more of my experience here:
Rmx2040 (realme 6i) scatter file
Hi guys, I'm trying to get the scatter file in this and so far I found this on the ozip file: preloader 0x0 pgpt 0x0 recovery_a 0x8000 misc 0x2008000 para 0x2088000 opporeserve1 0x2108000 opporeserve2
forum.hovatek.com
I'm subma rine13.
Joesh.lucas said:
Thanks for the information, I now understand that I should use the same boot.img. It was worth the experiment tho, I just hoped I did it better so I wouldn't have to go through this process again.
My phone is here with me. It's still stuck on red state and I haven't went to a service center to have it fixed yet. I went to Hovatek to look for some ways to fix this problem. I tried using miracle box and the SP flashtool method but the latter had problems with the scatter file and the former didn't get past this:
Waiting for USB Port...
Set OPPO PreLoader USB VCOM (Android) (COM4)
>>Please Hold "ON" to connect with the phone...
I also looked a little bit more into it and I found out that I can use the OFP file and the flasher application here: https://firmwarex.net/realme-6i-rmx2040-official-firmware/
But unfortunately, I can't use the application because it's asking for an OPPO ID or something. Either I bring this phone to a service center or I'll just let it be this way until I decide to sell it somewhere. I hope I'll be able to fix this on my own tho, at least, someday.
Edit:
You can read more of my experience here:
Rmx2040 (realme 6i) scatter file
Hi guys, I'm trying to get the scatter file in this and so far I found this on the ozip file: preloader 0x0 pgpt 0x0 recovery_a 0x8000 misc 0x2008000 para 0x2088000 opporeserve1 0x2108000 opporeserve2
forum.hovatek.com
I'm subma rine13.
Click to expand...
Click to collapse
Hey buddy i just rooted my realme 6i (RMX 2040) on build number A.37... everything went smooth and working flawlessly.... No system instabilities at all... Btw sorry to hear that your phone is still in brick state.. actually thing is oppo does not allow the users to flash stock rom on locked bl devices that why flasher tool asks for oppo authorized account in order to flash the device... And about SP flash tool.. it will not work either we have to wait for the patched rom that can be flashed on locked devices with sp flash tool
mehdi.shah said:
Hey buddy i just rooted my realme 6i (RMX 2040) on build number A.37... everything went smooth and working flawlessly.... No system instabilities at all... Btw sorry to hear that your phone is still in brick state.. actually thing is oppo does not allow the users to flash stock rom on locked bl devices that why flasher tool asks for oppo authorized account in order to flash the device... And about SP flash tool.. it will not work either we have to wait for the patched rom that can be flashed on locked devices with sp flash tool
Click to expand...
Click to collapse
Woah, is it true you've rooted it? How did you manage to pull it off? Is it similar to what I did except with different files?
Oh and yeah, I think I'll need to bring this to an authorized service center to have it fixed. In your currency, how much do you think it costs to flash the stock rom back to the phone? This has been a question that's been bothering me for months. I do hope it isn't pricey, because if it is then maybe I'll never have it fixed.
Joesh.lucas said:
Woah, is it true you've rooted it? How did you manage to pull it off? Is it similar to what I did except with different files?
Oh and yeah, I think I'll need to bring this to an authorized service center to have it fixed. In your currency, how much do you think it costs to flash the stock rom back to the phone? This has been a question that's been bothering me for months. I do hope it isn't pricey, because if it is then maybe I'll never have it fixed.
Click to expand...
Click to collapse
Yeah the procedure was the same as yours... I unlocked the bootloader i was on A27 build... And i downloaded the latest ozip file from the official site and i opened it up in file manager it asked if i want to update the software i clicked yes.. and it rebooted to stock recovery and started updating the device.. after successful update i opend up the ozip file by renaming it to .zip and extracted the boot.img and vbmeta.img. i patched the boot.img with latest magisk manager and tha than flashed those files in fastboot mode... With same commands that u used... And everything went well and its all good and rooted no problem at all..
And yeah the service center thing.. if its the software issue than the charge around 1.5 to 2k rupees in my country...which is around 9.34 to12.4 US dollars..
mehdi.shah said:
Yeah the procedure was the same as yours... I unlocked the bootloader i was on A27 build... And i downloaded the latest ozip file from the official site and i opened it up in file manager it asked if i want to update the software i clicked yes.. and it rebooted to stock recovery and started updating the device.. after successful update i opend up the ozip file by renaming it to .zip and extracted the boot.img and vbmeta.img. i patched the boot.img with latest magisk manager and tha than flashed those files in fastboot mode... With same commands that u used... And everything went well and its all good and rooted no problem at all..
And yeah the service center thing.. if its the software issue than the charge around 1.5 to 2k rupees in my country...which is around 9.34 to12.4 US dollars..
Click to expand...
Click to collapse
Does root work as it should?
Russian community guys reported that root exists in the system but not works at all. Rooting procedure looks the same.
sqzd0 said:
Does root work as it should?
Russian community guys reported that root exists in the system but not works at all. Rooting procedure looks the same.
Click to expand...
Click to collapse
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
I don't mean to be rude but, can you make a thread for that? Some rmx 2040 owners want to root their device and I think i just gave them a recipe for disaster.
Oh and by the way, thanks for answering my question. I have another one, will it be okay to update your device whilst rooted? If so then how do you stop the auto update?
(Sorry for the questions man hahahaha I wanted the same outcome but I failed miserably :| )
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
Bro give me boot.img a37
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
Give me boot.img of a37 version
mehdi.shah said:
Hey buddy i just rooted my realme 6i (RMX 2040) on build number A.37... everything went smooth and working flawlessly.... No system instabilities at all... Btw sorry to hear that your phone is still in brick state.. actually thing is oppo does not allow the users to flash stock rom on locked bl devices that why flasher tool asks for oppo authorized account in order to flash the device... And about SP flash tool.. it will not work either we have to wait for the patched rom that can be flashed on locked devices with sp flash tool
Click to expand...
Click to collapse
If you rooted dump the stock recovery and boot.img through terminal emulator I will try to port twrp
Boot.img and Vbmeta file can now be accessed by clicking the text above
Do is still need to relock my bootloader inorder to downgrade to A.27 update ? Thanks
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
Bro i tried the rooting process and i didnt check the boot and i rooted my phone the wifi,blueooth, camera, etc doesnt work anymore. If POSSIBLE can i revert it back to normal?
Can anyone provide me a twrp recovery file for realme 6i rmx2040 A.47 plsss