Hi, here I bring you a procedure for rooting your device using Magisk and Adb. I guess there is no need to say the risks involved in doing this.
First you'll need:
1. Having installed ADB on your pc, you can use this link: https://www.xda-developers.com/install-adb-windows-macos-linux/
2. Your device must have bootlader unlocked, here the process to do so: https://c.realme.com/in/post-details/1526491339024314368
3. The corresponding boot.img (In this thread you can find attached the file for RMX3301_11 global variant) or you can extracted by yourself from the ofp file using htis script https://github.com/bkerler/oppo_decrypt
Note: During the process I encountered that fastboot commands didn't seem to work, getting the message <<waiting for device>> when unloocking bootloader on windows 11.
This problem was caused due to the lack of proper drivers, if you face this problem there is a file with the needed drivers attached in this post as well.
Now rooting process:
1. You need to install the latest stable release of Magisk on your device, which you can find here: https://github.com/topjohnwu/Magisk
2. Copy the boot image to your device
3. Press the Install button in the Magisk card
4. Choose “Select and Patch a File” in method, and select the boot image, then connect your device via usb to your PC
5. Copy the patched image to your PC, move the file inside your platform-tools folder and rename it to patchedboot.img
6. Make sure usb debugging is turned on under developer options and give permission to your PC on your cellphone after typing the command adb devices on your ADB terminal
7. Type the command adb reboot bootloader
8. Once your device is on bootloader type de command fastboot devices to make sure your device is "attached".
9. Now type fastboot flash boot patchedboot.img
10. Reboot and open the Magisk app on your phone to check everything is ok.
Aditional stuff you might find useful:
Here you can find the Universal Safetynetfix module, which is working properly: https://github.com/blog2i2j/kdrag0n.._..safetynet-fix
You just need to flash it via magisk, reboot, turn on Zygysk and reboot again.
it is not work unlock app my phone
GT2 Pro RMX3301_11_A.16
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
arzuakay said:
it is not work unlock app my phone
GT2 Pro RMX3301_11_A.16
View attachment 5651113
Click to expand...
Click to collapse
[EU model] Unlock bootloader of European model
As you may know, at the time of writing it's not possible to unlock the bootloader of the European model. Fortunately there's a workaround. To know how it works, scroll to the end of the post. First of all, this is only for the European RMX3301...
forum.xda-developers.com
Where is the guide?
Please stop saying there is root or even bootloader unlock for the global variant. India is not "GLOBAL" aka the world, although you might like it to be.
Lol, I UBL EU Global phone with guide here on xda
Device doesn't boot anymore after flashing patchedboot.img
Ty
where is the boot.img for glabal RMX3301_11_C.13 android 13
Extract from Full OTA package.
It appears that Magisk 26.1 isnt able to root the GT2 Pro. I have flashed the patched boot image twice. First time it stuck around til I installed a module and restarted. Second time didnt even get root. I will try a third time with a canary version of Magisk.
Edit: Canary doesnt work either. Device keeps rebooting to bootloader. Flashed stock boot for now. Will try older version of magisk.
Edit2: Magisk 25.2 doesnt work either. All 3 versions flashed it just fine but device keeps reboot back to bootloader. Both slots too. Flashed back to stock boot.
I am on Indian version of Color Os 13.1 (C.19) so I assume India is not considered global. I will go flash a global rom I guess.
Magisk should work, drivers ok?
Stano36 said:
Magisk should work, drivers ok?
Click to expand...
Click to collapse
Flashes just fine as far as I can tell according to CMD (admin) but right after flashing, on reboot, it goes directly back to the bootloader (or switches to the other working slot). I just flashed the EUEX C.19 update using the OnePlus updater app and same thing.
Its weird because when I type "fastboot boot patchedboot.img" just to check if the patched boot image works, it boots fine with root working. But flashing using "fastboot flash boot patchedboot.com" goes into that "bricked" or "bootloop" status, whatever its called.
morphius88 said:
Flashes just fine as far as I can tell according to CMD (admin) but right after flashing, on reboot, it goes directly back to the bootloader (or switches to the other working slot). I just flashed the EUEX C.19 update using the OnePlus updater app and same thing.
Its weird because when I type "fastboot boot patchedboot.img" just to check if the patched boot image works, it boots fine with root working. But flashing using "fastboot flash boot patchedboot.com" goes into that "bricked" or "bootloop" status, whatever its called.
Click to expand...
Click to collapse
adb reboot bootloader
fastboot devices (identified)
fastboot flash boot patchedboot.img
fastboot reboot
Stano36 said:
adb reboot bootloader
fastboot devices (identified)
fastboot flash boot patchedboot.img
fastboot reboot
Click to expand...
Click to collapse
Thats pretty much exactly what I do. See screenshot attached from my last attempt using stable Magisk 26.1 patched boot image. The reboot goes back to bootloader.
morphius88 said:
Thats pretty much exactly what I do. See screenshot attached from my last attempt using stable Magisk 26.1 patched boot image. The reboot goes back to bootloader.
Click to expand...
Click to collapse
Use this command before flashing the patched boot.img and try again
fastboot set_active a
Click to expand...
Click to collapse
NumberOneDz said:
Use this command before flashing the patched boot.img and try again
Click to expand...
Click to collapse
I've tried that too, it does the same result in either slot.
The funny thing is, using "flash boot patchedboot.img" works fine but that is obviously temporary so I dont understand why it doesnt want to stick if the temporary rooted boot works fine.
Edit: see screenshot, I ran fastboot getvar all after flashing patched boot to both slots. I will flash stock boot to get back to a workable phone for now.
morphius88 said:
It appears that Magisk 26.1 isnt able to root the GT2 Pro. I have flashed the patched boot image twice. First time it stuck around til I installed a module and restarted. Second time didnt even get root. I will try a third time with a canary version of Magisk.
Edit: Canary doesnt work either. Device keeps rebooting to bootloader. Flashed stock boot for now. Will try older version of magisk.
Edit2: Magisk 25.2 doesnt work either. All 3 versions flashed it just fine but device keeps reboot back to bootloader. Both slots too. Flashed back to stock boot.
I am on Indian version of Color Os 13.1 (C.19) so I assume India is not considered global. I will go flash a global rom I guess.
Click to expand...
Click to collapse
You need to flash vbmeta with disabled verification:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rapper_skull said:
You need to flash vbmeta with disabled verification:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Thank you for this. I think this did it. First time I had to disable verity on any phone to get root as far as I know.
I now have root and pass Safety Net.
@vanya.ag you might need to put that in your original post in case there are others that run into the same situation.
Related
First off, I don't know if this is the perfect place for this thread so I apologize in advance.
I have a HTC Evo 4G LTE and I accidentally wiped everything with TWRP. It can boot to the bootloader/fastboot menus and TWRP no problem, but I can't install anything. Maybe i'm just doing everything in the wrong order. Both the SD card and the Internal SD cards have been formatted to what they're supposed to be (caused me a bit of trouble at first). My phone is set to S-On, which is a pain in the ass, because from what I understand I can't turn it off to flash a new ROM without an OS, which I don't have. Every time I attempt to install the stock ROM for my device the phone restarts when attempting to install the kernel, included in the ROM. I borrowed my friend's identical phone, rooted it and installed TWRP, created a backup, moved the backup to my phone's ext SD card and attempted to recover off of that but my TWRP can't find any of the files, but they show up just fine with the file explorer.
I've properly srewed myself. Any advice?
windowpuncher said:
First off, I don't know if this is the perfect place for this thread so I apologize in advance.
I have a HTC Evo 4G LTE and I accidentally wiped everything with TWRP. It can boot to the bootloader/fastboot menus and TWRP no problem, but I can't install anything. Maybe i'm just doing everything in the wrong order. Both the SD card and the Internal SD cards have been formatted to what they're supposed to be (caused me a bit of trouble at first). My phone is set to S-On, which is a pain in the ass, because from what I understand I can't turn it off to flash a new ROM without an OS, which I don't have. Every time I attempt to install the stock ROM for my device the phone restarts when attempting to install the kernel, included in the ROM. I borrowed my friend's identical phone, rooted it and installed TWRP, created a backup, moved the backup to my phone's ext SD card and attempted to recover off of that but my TWRP can't find any of the files, but they show up just fine with the file explorer.
I've properly srewed myself. Any advice?
Click to expand...
Click to collapse
Since you are s-on you need to flash the rom twice.
BD619 said:
Since you are s-on you need to flash the rom twice.
Click to expand...
Click to collapse
I am new to ROM flashing, I just kind of got thrown into it, lol. Please elaborate? I'm assuming flashing is installing the rom with TWRP. I flash the rom, wipe cache/dalvik, then flash again? I'll try it then post results in a minute.
Result: Doesn't work, when it says "installing Kernel, please wait...", it stays on that message for a minute or so then the phone attempts to reboot into a nonexistant OS, effectively stopping itself so I have to restart into TWRP again with no progress made.
I think you want to let it reboot in between the two flashes. I have no idea why it makes a difference, but it does.
Sent from my EVO LTE using XDA Premium 4 mobile app
Read this:
http://forum.xda-developers.com/showthread.php?t=2443108
Some Sense ROM's include a kernel installer to help facilitate flashing while S-on. You'll need to check the ROM OP and see. Otherwise the kernel can be flashed via fastboot. For more info hit the top link in my sig.
Sent from my HTC device
fizbanrapper said:
I think you want to let it reboot in between the two flashes. I have no idea why it makes a difference, but it does.
Sent from my EVO LTE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It can't. It reboots while attempting to install the kernel then freezes because there's no OS to boot to.
Try flashing the kernel first. Extract the boot.img file from the ROM zip archive using your computer. Then, with the phone connected to the PC via USB, boot into the bootloader and go to fastboot. It should change to "fastboot USB". Then use the fastboot tool from a command prompt to verify connectivity and flash the kernel.
To verify connectivity, type fastboot devices. You should see your device's serial number of its connected properly.
To flash the kernel, type fastboot flash boot boot.img. If the boot.img file and fastboot executable are in different directories, you'll need to include the path to the file. Or just put them in the same directory.
Once you've flashed the kernel, try flashing the ROM through recovery again.
Sent from my EVO using Tapatalk
CornDogg said:
Try flashing the kernel first. Extract the boot.img file from the ROM zip archive using your computer. Then, with the phone connected to the PC via USB, boot into the bootloader and go to fastboot. It should change to "fastboot USB". Then use the fastboot tool from a command prompt to verify connectivity and flash the kernel.
To verify connectivity, type fastboot devices. You should see your device's serial number of its connected properly.
To flash the kernel, type fastboot flash boot boot.img. If the boot.img file and fastboot executable are in different directories, you'll need to include the path to the file. Or just put them in the same directory.
Once you've flashed the kernel, try flashing the ROM through recovery again.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Doesn't work. I can plug my phone in all I want but it will never change to fastboot usb. It stays in fastboot just fine and I can still boot TWRP, but there's no fastboot usb. I've reinstalled drivers and tried 32 bit LiveCD ubuntu. I may need to install firmware on this stupid phone.
From the main bootloader screen, you're pressing the power button on fastboot to go into fastboot, right? And from there you can never get it to go to fastboot USB?
Sent from my EVO using Tapatalk
If you're on the old partition layout have you followed my guide that I posted previously and tried to install MeanBean ROM?
Sent from my HTC device
CornDogg said:
From the main bootloader screen, you're pressing the power button on fastboot to go into fastboot, right? And from there you can never get it to go to fastboot USB?
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Yes, that was the case.
HOWEVER, I screwed up again. I reinstalled Ubunto on my laptop and now fastboot usb works just fine.
Sometimes it hurts to live. Now I just need to find out how to flash with fastboot on ubuntu.
windowpuncher said:
Yes, that was the case.
HOWEVER, I screwed up again. I reinstalled Ubunto on my laptop and now fastboot usb works just fine.
Sometimes it hurts to live. Now I just need to find out how to flash with fastboot on ubuntu.
Click to expand...
Click to collapse
Progress.
To get the fastboot binaries on Ubuntu, you can either download and install the Android SDK and install the platform tools or go download DirtyRacun from unlimited.io. The binaries are included in the .tar archive. You may need to use the chmod command on the fastboot and adb binaries to add permissions to execute the binaries.
Once you have the binaries executable, the commands are the same, except you'll have to elevate with sudo. So, assuming you're working in the directory where you have the fastboot executable and the boot.img file, the commands would be:
sudo ./fastboot devices
sudo ./fastboot flash boot boot.img
CornDogg said:
Progress.
To get the fastboot binaries on Ubuntu, you can either download and install the Android SDK and install the platform tools or go download DirtyRacun from unlimited.io. The binaries are included in the .tar archive. You may need to use the chmod command on the fastboot and adb binaries to add permissions to execute the binaries.
Once you have the binaries executable, the commands are the same, except you'll have to elevate with sudo. So, assuming you're working in the directory where you have the fastboot executable and the boot.img file, the commands would be:
sudo ./fastboot devices
sudo ./fastboot flash boot boot.img
Click to expand...
Click to collapse
fter I
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what happens. My phone just sits there, the screen doesn't change, but it does say Fastboot USB. I restarted my phone but it got stuck at the dev boot screen with legal warnings in red text.
Addition: Booted to recovery to flash the ROM zip, not just the boot image, still restarts when attempting to install the Kernel.
The screen on your phone won't change when flashing the kernel with fastboot. After flashing it, press the power button on Fastboot to go back to the main bootloader screen and go to recovery to get into TWRP. From there, flash the .zip of the ROM that you pulled boot.img from like you normally would from TWRP (Install, select .zip, wipe cache/data, etc).
CornDogg said:
The screen on your phone won't change when flashing the kernel with fastboot. After flashing it, press the power button on Fastboot to go back to the main bootloader screen and go to recovery to get into TWRP. From there, flash the .zip of the ROM that you pulled boot.img from like you normally would from TWRP (Install, select .zip, wipe cache/data, etc).
Click to expand...
Click to collapse
I just did this, and the phone gets stuck at the dev boot screen that says HTC with the red legal text.
Have you tried a different ROM? Maybe try CM or Viper 4G. If you go the Viper 4G route, try this one: http://forum.xda-developers.com/showthread.php?t=2124391
I think the newest Viper 4G changes the partition layout or something, so I think that would just further complicate things at the moment.
CornDogg said:
Have you tried a different ROM? Maybe try CM or Viper 4G. If you go the Viper 4G route, try this one: http://forum.xda-developers.com/showthread.php?t=2124391
I think the newest Viper 4G changes the partition layout or something, so I think that would just further complicate things at the moment.
Click to expand...
Click to collapse
Yeah, I think I'll try cyanogenmod or stock android. Thank you for the suggestion, now i'll go see if it works.
No problem. If you decide to go the CM route, deck's CM11 is pretty great.
http://forum.xda-developers.com/showthread.php?t=2518211
Good luck!
CornDogg said:
No problem. If you decide to go the CM route, deck's CM11 is pretty great.
http://forum.xda-developers.com/showthread.php?t=2518211
Good luck!
Click to expand...
Click to collapse
I went on with installing DirtyRacun (http://unlimited.io/jewel.htm) and made it to step 12. As my phone ws rebooting it once again got stuck at that HTC red text dev warning screen. So now i'm stuck again.
windowpuncher said:
I went on with installing DirtyRacun (http://unlimited.io/jewel.htm) and made it to step 12. As my phone ws rebooting it once again got stuck at that HTC red text dev warning screen. So now i'm stuck again.
Click to expand...
Click to collapse
I didn't use DirtyRacun to S-OFF (I used RumRunner), so I can't speak on this with much authority. Just to confirm I understand correctly, though, you flashed the RUU (step 9), rebooted into the bootloader (step 10), and re-did the HTC Dev Unlock (step 11). Then, as it's booting up into the ROM installed via the RUU, it gets stuck?
Were you able to get anywhere with flashing Cyanogenmod? Or did you just decide to go through the S-OFF process instead?
Hi all,
For those who don't know, I'm known for rooting HMD Nokia Android Phones.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So after few hours testing, I finally found out how to root it.
Note, I've only dumped stock ROM from Verizon Wireless Variant as it's the only variant I've obtained so far. For non-operator variant and AT&T variant, I need your help for firmware dumping in case you want to restore your phone back to factory original state or OTA update if possible.
Known working build: H1A1000.010ho.01.01.01r.109
Procedure is pretty regular.
Step 1: Unlock the bootloader
Unlike HMD Nokia Android Phones, bootloader unlock is straight forward.
Just enable OEM unlocking in developer options, reboot your phone to Fastboot mode and unlock the bootloader with following command:
Code:
fastboot flashing unlock
Then confirm unlock on the phone.
As I've always recommended for HMD Nokia Phones, you should do critical unlock as well:
Code:
fastboot flashing unlock_critical
Then confirm unlock on the phone.
Strange enough, this phone doesn't have unlock warning after unlocked. Not sure about open market release or AT&T Variant.
Step 2: Install Magisk Manager and allow storage permission
You can download it from Magisk release topic or https://github.com/topjohnwu/magisk/releases
Step 3: Reboot to fastboot mode and flash patched boot image
You can download required patched boot image and representative stock boot image from here: https://www.androidfilehost.com/?w=files&flid=297410
For Verizon Variant that available with build "H1A1000.010ho.01.01.01r.109" so far, download "H1A1000.010ho.01.01.01r.109-boot_magisk_patched_193.img". You can check software version yourself if correct.
The command is straight forward too:
Code:
fastboot flash boot /path/to/H1A1000.010ho.01.01.01r.109-boot_magisk_patched_193.img
If you use Platform tools from Google officially, you needn't to care about your current slot actually.
Now reboot your phone:
Code:
fastboot reboot
Step 4: Restore stock boot image and reinstall Magisk (For OTA update ability although no update for months)
After your phone booted, enable USB debugging and copy the file "H1A1000.010ho.01.01.01r.109-boot.img" you downloaded along with patched boot image. I would assume you copied it to root directory of internal storage.
So execute following ADB commands:
Code:
$ su
(Confirm Root permission on the phone)
# getprop ro.boot.slot_suffix
If it returns a, you'll need to execute this command:
Code:
# dd if=/storage/emulated/0/H1A1000.010ho.01.01.01r.109-boot.img of=/dev/block/bootdevice/by-name/boot_a
If it returns b, you'll need to execute this command:
Code:
# dd if=/storage/emulated/0/H1A1000.010ho.01.01.01r.109-boot.img of=/dev/block/bootdevice/by-name/boot_b
Then open Magisk Manager on your phone, tap no thanks if it asks for extra modules, then tap "Install" at the right of Magisk version, choose "Direct Install", and wait for the procedure complete.
If installed successfully, you can reboot your phone on Magisk Manager now.
That's it!
At least this phone will work with Treble GSI build, so you should have idea about how could I dump the phone.
For Treble GSI report, read this: https://github.com/phhusson/treble_experimentations/wiki/Red-Hydrogen-One
For those who want to know how I dumped the phone:
Well, I found the phone could support Treble GSI and received update before.
So if your current slot is B, you definitely want to give it a try.
1. Unlock the bootloader
2. Download AOSP 8.1 Treble GSI from @phhusson 's repo:
https://github.com/phhusson/treble_experimentations/releases
In my case I chose system-arm64-ab-gapps-su.img.xz one
3. Enter fastboot mode and flash the image
Please check current slot as well
Code:
fastboot getvar current-slot
I would assume your current slot is B in this case.
Code:
fastboot flash system /path/to/system-arm64-ab-gapps-su.img
fastboot erase frp
4. Use volume key to choose "Reboot to recovery" then press power key to confirm
Press power key and volume up key to get the menu if "No command" appears, then choose "Wipe data/factory reset" to erase userdata storage.
Then reboot the phone.
5. After the phone booted, finish Setup Wizard.
6. Dump the boot image
Code:
adb shell
$ su
(Confirm root permission on the phone)
# dd if=/dev/block/bootdevice/by-name/boot_b of=/storage/emulated/0/stock_boot.img
# exit
$ exit
adb pull /storage/emulated/0/stock_boot.img
adb reboot bootloader
7. Switch to previous version, do factory reset
Code:
fastboot --set-active=a
Reboot to recovery and perform factory reset.
8. Reboot to normal OS and accept OTA update.
9. Use Magisk to patch the boot image you dumped, then root it with your patched boot image, or you can upload it if possible.
10. You can dump other partitions as well if you want.
Reserved 2
How to unlock the titanium alloy version?
great man! but H1T1000 ？How to unlock the titanium alloy version? Which one does boot. img use?
mavitz said:
great man! but H1T1000 ？How to unlock the titanium alloy version? Which one does boot. img use?
Click to expand...
Click to collapse
For Titanium variant H1T1000, I don't have the phone right away.
If you can assist me, I'd like to help you for H1T1000 firmware dumping and rooting.
你好，你也是中国人呀？能加一下QQ吗？我的QQ361212944 ，我进开发者里面OEM锁打勾了，然后进fastboot模式，输入那两个命令，都提示出错。希望你能帮帮忙。谢谢。
Well Sir
Just performed this procedure on my VZW black aluminum model and yup got ROOT! Everything works and is stable so far. 4view is working, camera is shooting 3D just fine. Not a single error, stopped app, like I said everything is chugging along. So sweet! Thanks man. I almost tried this exact procedure on my own but discussions in the h4vuser.net forums swayed me away. Just happy to have root access on my H1!
the H1 open market needs unlock code
Hey guys I ****ed up pretty big. Red wants me to send in my phone to get reimaged.
Can someone please dump their system.img for me.
https://www.addictivetips.com/mobil...es-boot-recovery-and-system-partition-images/
SynxSynx said:
Hey guys I ****ed up pretty big. Red wants me to send in my phone to get reimaged.
Can someone please dump their system.img for me.
https://www.addictivetips.com/mobil...es-boot-recovery-and-system-partition-images/
Click to expand...
Click to collapse
dump is here
https://github.com/AndroidDumps/red_hydrogenone_dump
joeyw007 said:
dump is here
https://github.com/AndroidDumps/red_hydrogenone_dump
Click to expand...
Click to collapse
Thank you so so much dude.
SynxSynx said:
Thank you so so much dude.
Click to expand...
Click to collapse
your welcome, hope it helps.
joeyw007 said:
your welcome, hope it helps.
Click to expand...
Click to collapse
I"m a little bit dense when it comes to this. I'm assuming this is the full oTA image that was captured somehow. Do I just repackage the whole thing into a zip, drop it on an SD card and then update through recovery mode? My flashing experience is kind of limited to just nexus devices which are notoriously easy.
SynxSynx said:
I"m a little bit dense when it comes to this. I'm assuming this is the full oTA image that was captured somehow. Do I just repackage the whole thing into a zip, drop it on an SD card and then update through recovery mode? My flashing experience is kind of limited to just nexus devices which are notoriously easy.
Click to expand...
Click to collapse
An official rom does not exist for this phone. at least not one we can access. That's why it's SUPER IMPORTANT not to make any booboos with rooting this phone. This is just a dump from a bone stock phone. I'm not sure, you're going to have to do some homework to see if it's even possible. I would think flashing the boot.img to the current boot slot Magisk patched should fix the issue depending on what caused it. Maybe someone else could chime in with a little more expertise on the matter. Never used a phone dump to create *.img file to flash via fastboot, if it's even possible. If you get it working and try to re root stop after step three do not perform the tasks in step four and turn off automatic system updates in dev options.
joeyw007 said:
An official rom does not exist for this phone. at least not one we can access. That's why it's SUPER IMPORTANT not to make any booboos with rooting this phone. This is just a dump from a bone stock phone. I'm not sure, you're going to have to do some homework to see if it's even possible. I would think flashing the boot.img to the current boot slot Magisk patched should fix the issue depending on what caused it. Maybe someone else could chime in with a little more expertise on the matter. Never used a phone dump to create *.img file to flash via fastboot, if it's even possible. If you get it working and try to re root stop after step three do not perform the tasks in step four and turn off automatic system updates in dev options.
Click to expand...
Click to collapse
Right for sure, but the thing is I think I messed up at the point where I ended up not being able to get it to boot after removing the stock facebook apps (Lord knows why) but I did get t successfully rooted. Once it hit that point I kind of panicked and ended up
c:\adb>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system_b'...
OKAY [ 0.354s]
finished. total time: 0.356s
That was my dun goofed point.
At this point it's now flashing to a boot_a slot where it used to be flashing to boot_b slot. I am able to get it to start loading the OS but I'm not sure why it's not actually booting. It makes it to the Verizon boot screen, but then just hangs there.
My request from you earlier to see if you could dump your system.img (Which should still be bone stock and doesn't contain user data) was to see if I flashed the system from fastboot it would work.
I think bootloader wise it's totally fine, it's just I can't get the system to boot.
So I'm not really looking for a rom-per-se I just want to see if I can get the system.img from someones (now rooted) device to see if loading it through fastboot will make it so I don't have to send it in and wait for 5 days to get my phone back
Yeah it's completely hosed. If anyone who's rooted can do the following steps for me, I would really appreciate it because I have no phone at the moment.
adb shell
su
ls -al /dev/block/platform/*/by-name
read the Partition Management Table and find something that looks like
system ---> /dev/block/mmcblk07
dd if=/dev/block/mmcblk07 of=/sdcard/system.img
then upload the ~3gb file
It's basically the only thing that will save me right now.
So I did some digging as I had no choice. I basically found that the hydrogen one doesn't use mmcblk's so I was giving bad info.
I worked with a friend who helped compile TWRP for the H1A1000 which can be found here https://androidfiles.host/2RE~i?cb1f802841522869ba768a30999b613a
You can use this by going into fastboot and doing fastboot flash boot twrp-3.3.1-0-HydrogenONE.img
If someone P L E A S E can load twrp
go into advanced>terminal
ls /dev/block/by-name
find their system_a and system_b mountpoints (Mine were sda6 and sda8 respectively) and then do
dd if=/dev/block/sda6 of=/sdcard/system_a.img
dd if=/dev/block/sda8 of=/sdcard/system_b.img
then upload those files to a mega
I would really really really like 100% totally appreciate it. Like I'll throw you 20$ at this point just for the trouble.
SynxSynx said:
So I did some digging as I had no choice. I basically found that the hydrogen one doesn't use mmcblk's so I was giving bad info.
I worked with a friend who helped compile TWRP for the H1A1000 which can be found here https://androidfiles.host/2RE~i?cb1f802841522869ba768a30999b613a
You can use this by going into fastboot and doing fastboot flash boot twrp-3.3.1-0-HydrogenONE.img
If someone P L E A S E can load twrp
go into advanced>terminal
ls /dev/block/by-name
find their system_a and system_b mountpoints (Mine were sda6 and sda8 respectively) and then do
dd if=/dev/block/sda6 of=/sdcard/system_a.img
dd if=/dev/block/sda8 of=/sdcard/system_b.img
then upload those files to a mega
I would really really really like 100% totally appreciate it. Like I'll throw you 20$ at this point just for the trouble.
Click to expand...
Click to collapse
Like FIH made HMD Nokia phones, I've created fastboot image for H1A1000 (Verizon only).
I will upload that to AFH soon.
hikari_calyx said:
Like FIH made HMD Nokia phones, I've created fastboot image for H1A1000 (Verizon only).
I will upload that to AFH soon.
Click to expand...
Click to collapse
Dude thank you so much.
edit, read your profile, donation link secured
To subscribers of this topic:
raw dump of H1A1000 for Verizon uploaded. Note, system and vendor images are raw ext4 images, use img2simg to process them if you want to use fastboot to flash it.
https://www.androidfilehost.com/?fid=1899786940962611843
Obs: these were the steps that i did to get it, try it by your own risk
----------------------update------------------------
Some people are saying that can't get the 11.1.021 via ota from zui10, but I got the information that this version of qfil 11.1.021 is getting ota to the 11.5, so you should try it just changing the files in the tutorial of step 1 and if don't get the ota, jump to the step 3
-------------------------------------------------------
I did the first part with my bootloader locked, and just got it working this way. I tried to qfil directly the 11.1.021 or use the version updated with the bootloader unlocked but i got error 7 later.
To start, you will need adb and fastboot, and you can get them from here
1- Qfil the zui 10 version from this tutorial
2- Set up a pin (it will be important) and update the zui to version 11.1.021 (right after you install the zui 10 it will pop the update, if not you can use the zui update app)
3- Now that you have 11.1.021 from ota you have to go to fastboot mode (adb reboot bootloader) and unlock your bootloader, if you do this on zui 10 or zui 11.5 you will got on bootloop and have to start all again (tutorial <- you can use this to lock your bootloader for start the proccess too)
4- Go again to bootloader and use fastboot flash recovery twrp.img (download twrp)
5- From fastboot mode, press volume down repeatly until you see "Recovery mode" then press power button, the phone will reboot twice and enter in twrp, you will need to put the pin set on step 2
6- Pass this update zip to your phone from the PC then select it on "install" section and swipe to flash (this was the step where i got error 7 with qfil version of 11.1.021, if you got this, the only solution i know is start all over again owith qfil zui 10)
7- After flash is done, go back to the home page of twrp, select "wipe" and mark "dalvik", "cache" and "data" then reboot system
Your phone will be on bootloop and this is the part that i discover after 2 days trying
8- Turn off your phone and turn it back pressing the power button and the volume down to enter in fastboot mode, you will see on last line that your bootloader will be locked again, and this is the cause of bootloop
9- Use the commands to unlock bootloader again (fastboot flash unlock your_unlock_img.img and fastboot oem unlock-go)
Your phone will boot and reboot in twrp that will do an automatic process, than will reboot again in ZUI 11.5.141 (may take some minutes)
Obs²: After this proccess, if you want to use TWRP to install a rom or something, you will need to flash it again
when I try to install just I got error 7 for everstep :S how can I solve it ?
brujaboy said:
when I try to install just I got error 7 for everstep :S how can I solve it ?
Click to expand...
Click to collapse
Did you try it from qfil the zui 10 with the locked bootloader?
Because i got this error when i ota updated from 10 to 11.1.021 with the bootloader unlocked
Astronomico said:
Did you try it from qfil the zui 10 with the locked bootloader?
Because i got this error when i ota updated from 10 to 11.1.021 with the bootloader unlocked
Click to expand...
Click to collapse
yes I did my friend I installed zui10 with QFIL after that I ınstalled 11.0.21 with twrp and when I try to install 11.5 I got error 7, I did edit with notepad++ but still have this problem
brujaboy said:
yes I did my friend I installed zui10 with QFIL after that I ınstalled 11.0.21 with twrp and when I try to install 11.5 I got error 7, I did edit with notepad++ but still have this problem
Click to expand...
Click to collapse
I think the problem is with the version you're installing in TWRP , after qfil zui10, wait for the OTA for 11.1.021 of the app zui update, it seems to exist some versions of 11.1.021 and the TWRP version is not the same of the OTA
The version of 11.1.021 that i've got by OTA with my bootloader already unlocked on zui10 got error 7 too, just the version i've got with the bootloader locked worked
Astronomico said:
I think the problem is with the version you're installing in TWRP , after qfil zui10, wait for the OTA for 11.1.021 of the app zui update, it seems to exist some versions of 11.1.021 and the TWRP version is not the same of the OTA
The version of 11.1.021 that i've got by OTA with my bootloader already unlocked on zui10 got error 7 too, just the version i've got with the bootloader locked worked
Click to expand...
Click to collapse
we need wait thank u bro
Microsoft Windows [Version 10.0.18362.657]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot> adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Fixed
this is whilest in fastboot.. ^^
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment 4951729
it pushes a command when phone was on but when in fastboot / bootloader nothing ? any ideas?
Fixed
every time i push recovery img twrp via ADB it gets bootloader loop
leerh said:
every time i push recovery img twrp via ADB it gets bootloader loop
Click to expand...
Click to collapse
That's weird, i've uploaded the same img i used on mine smartphone, it reboot twice, but starts after in my case, i just got bootloop after unlock the bootloader, but never after flash the twrp...
Try to turn your phone on holding the vol down button to enter in fastboot and check if it's really unlocked, since you flashed the twrp, you will need it
Btw, try to use the files of this tutorial
Astronomico said:
That's weird, i've uploaded the same img i used on mine smartphone, it reboot twice, but starts after in my case, i just got bootloop after unlock the bootloader, but never after flash the twrp...
Try to turn your phone on holding the vol down button to enter in fastboot and check if it's really unlocked, since you flashed the twrp, you will need it
Btw, try to use the files of this tutorial
Click to expand...
Click to collapse
yhyh it says device is unlocked ive used unlock image from lenovo site to unlock it.
im currently on 11.1.021 st cant install twrp affter installing keeps booting to bootloader (unlocked) from here i will need to use qfill to get stock firmware 10.5.304 cn version stock recovery still works
ive also tried on ZUI_10.5.304 same thing
qill emergency flash dose not lock bootloader for me? well i cant twrps anymore makes me feel its step away from total brick
do i need to lock it then qfill then 11.1.021st via OTA then unlock it
I've Just googled It and i found that flash magisk could repair the twrp bootloop, because magisk changes the boot.img that is the cause of the problem
You can download It on magiskmanager site, put it on your phone, than use twrp install session to flash it
And Qfil doesn't Lock your bootloader
Astronomico said:
I've Just googled It and i found that flash magisk could repair the twrp bootloop, because magisk changes the boot.img that is the cause of the problem
You can download It on magiskmanager site, put it on your phone, than use twrp install session to flash it
And Qfil doesn't Lock your bootloader
Click to expand...
Click to collapse
thanks for looking into it for me and i will try this out now and let you know the results done.
this a fresh from factory flash so there is no magisk modules. can you post the links to the information you found.. i cant flash any files affter installing twrps which is successful the via ADB but affter the reboot or trying twrps or access phone or recovery will bootloop my phone to go into fast boot every single time...
can i install twrps on 10.304 and 11.021 both are offical cn roms? device has to be unlocked right which it is? is there any place i can get stock recovry image?
i wanna try= fastboot flash boot_a stockboot.img=fastboot flash boot_b stockboot.img
but i dont think i should as qfil provides stock factory flash? means its fully fresh?
leerh said:
thanks for looking into it for me and i will try this out now and let you know the results done.
this a fresh from factory flash so there is no magisk modules. can you post the links to the information you found.. i cant flash any files affter installing twrps which is successful the via ADB but affter the reboot or trying twrps or access phone or recovery will bootloop my phone to go into fast boot every single time...
can i install twrps on 10.304 and 11.021 both are offical cn roms? device has to be unlocked right which it is? is there any place i can get stock recovry image?
i wanna try= fastboot flash boot_a stockboot.img=fastboot flash boot_b stockboot.img
but i dont think i should as qfil provides stock factory flash? means its fully fresh?
Click to expand...
Click to collapse
Oh, i thought you could access the twrp after install it, sorry
The tutorial on step 1 provides the official cn rom zui10, if you use it, your phone will probably boot normally.
I think you should lock your bootloader and use the official, you will have the updates via OTA, since you can't use TWRP, I think it will be the best for you, I don't know how help you more :/
I have a request anyone can share with my twrp back up clear update without data like zip file because I have problem with my QFIL and when I try to install zui 10.5 give me sahara error and I thought about this option
brujaboy said:
I have a request anyone can share with my twrp back up clear update without data like zip file because I have problem with my QFIL and when I try to install zui 10.5 give me sahara error and I thought about this option
Click to expand...
Click to collapse
Sorry, i didn't see it, but saraha error is probably caused because wrong version of USB drivers in your PC, or you're being too slow to press "download content" on qfil after plug the phone (I don't know exactly why, but you have to click it fairly fast)
Astronomico said:
Sorry, i didn't see it, but saraha error is probably caused because wrong version of USB drivers in your PC, or you're being too slow to press "download content" on qfil after plug the phone (I don't know exactly why, but you have to click it fairly fast)
Click to expand...
Click to collapse
doesn't matter, thank u so much for replying yesterday I installed all of driver versions but I saw still again and I find another method like pushing very fast download click button and I did successfully 11.1.021 thank u so much again for supporting
Astronomico said:
Obs: these were the steps that i did to get it, try it by your own risk
I did the first part with my bootloader locked, and just got it working this way. I tried to qfil directly the 11.1.021 or use the version updated with the bootloader unlocked but i got error 7 later.
To start, you will need adb and fastboot, and you can get them from here
1- Qfil the zui 10 version from this tutorial
2- Set up a pin (it will be important) and update the zui to version 11.1.021 (right after you install the zui 10 it will pop the update, if not you can use the zui update app)
3- Now that you have 11.1.021 from ota you have to go to fastboot mode (adb reboot bootloader) and unlock your bootloader, if you do this on zui 10 or zui 11.5 you will got on bootloop and have to start all again (tutorial <- you can use this to lock your bootloader for start the proccess too)
4- Go again to bootloader and use fastboot flash recovery twrp.img (download twrp)
5- From fastboot mode, press volume down repeatly until you see "Recovery mode" then press power button, the phone will reboot twice and enter in twrp, you will need to put the pin set on step 2
6- Pass this update zip to your phone from the PC then select it on "install" section and swipe to flash (this was the step where i got error 7 with qfil version of 11.1.021, if you got this, the only solution i know is start all over again owith qfil zui 10)
7- After flash is done, go back to the home page of twrp, select "wipe" and mark "dalvik", "cache" and "data" then reboot system
Your phone will be on bootloop and this is the part that i discover after 2 days trying
8- Turn off your phone and turn it back pressing the power button and the volume down to enter in fastboot mode, you will see on last line that your bootloader will be locked again, and this is the cause of bootloop
9- Use the commands to unlock bootloader again (fastboot flash unlock your_unlock_img.img and fastboot oem-unlock go)
Your phone will boot and reboot in twrp that will do an automatic process, than will reboot again in ZUI 11.5.141 (may take some minutes)
Obs²: After this proccess, if you want to use TWRP to install a rom or something, you will need to flash it again
Click to expand...
Click to collapse
Hi bro. I see a little error in your command: The second command in the 9th step is wrong, the correct command is: "fastboot oem unlock-go".
Greetings.
leerh said:
yhyh it says device is unlocked ive used unlock image from lenovo site to unlock it.
im currently on 11.1.021 st cant install twrp affter installing keeps booting to bootloader (unlocked) from here i will need to use qfill to get stock firmware 10.5.304 cn version stock recovery still works
ive also tried on ZUI_10.5.304 same thing
qill emergency flash dose not lock bootloader for me? well i cant twrps anymore makes me feel its step away from total brick
do i need to lock it then qfill then 11.1.021st via OTA then unlock it
Click to expand...
Click to collapse
i got step 1,2,3,4,5 and 6, got an error #7.
so i used the tutorial to flash the device in step 1
it was unable to update cuz bootloader was unlock
i locked bootloader and update to 11.1.021
so afther that, i unlocked again to install twrp.
intalled twrp and transfer file to phone
booted twrp and installed the zip, got the error 7 again.
lipeneiva said:
i got step 1,2,3,4,5 and 6, got an error #7.
so i used the tutorial to flash the device in step 1
it was unable to update cuz bootloader was unlock
i locked bootloader and update to 11.1.021
so afther that, i unlocked again to install twrp.
intalled twrp and transfer file to phone
booted twrp and installed the zip, got the error 7 again.
Click to expand...
Click to collapse
best thing is to try again an follow every letter and step this only way to install 11.5 (beta) did u set a pin it is needed ive not seen another guide to install android 10
Lombachita said:
Hi bro. I see a little error in your command: The second command in the 9th step is wrong, the correct command is: "fastboot oem unlock-go".
Greetings.
Click to expand...
Click to collapse
Ops, fixed
Will there be a TWRP version compatible with oxygen os V14 currently running on European Nord 2?
I tried previous TWRP guides for the Nord 2 but it didn't work.
Recovery OS's like TWRP works with all versions of the nord2 regardless of the update version.
More than likely you didn't follow all steps correctly. There are multiple mistakes you can make which results in the stock recovery OS being reflashed and the TWRP recovery being overwritten; I'm not completely sure of all the scenarios in which this happens, but you definitely made a miss-step somewhere.
I'm also running an EU nord variant with V14 and TWRP works fine, I've just noticed that after a few reboots TWRP partition gets overwritten by the stock OS again, in which case I just simply reflash the TWRP if i need to use it.
Zombnombs said:
Recovery OS's like TWRP works with all versions of the nord2 regardless of the update version.
More than likely you didn't follow all steps correctly. There are multiple mistakes you can make which results in the stock recovery OS being reflashed and the TWRP recovery being overwritten; I'm not completely sure of all the scenarios in which this happens, but you definitely made a miss-step somewhere.
I'm also running an EU nord variant with V14 and TWRP works fine, I've just noticed that after a few reboots TWRP partition gets overwritten by the stock OS again, in which case I just simply reflash the TWRP if i need to use it.
Click to expand...
Click to collapse
oh..ok i didn't know this. Thanls for the information
I actually followed the steps.
fastboot devices -> then flash the vbmeta -> then flash TWRP -> but then i cannot switch to the Recovery anymore.
Booting the phone works fine but i cannot access the recovery anymore and it always directly jumps me back to fastboot mode. I followed several videos and tutorials here but whatever i do what works for others seems to not work for me
Whenever i try it seems like the recovery is gone. Even stock recovery is not accessable anymore. I wonder what i did wrong or if i need to flash other files too.
Copaxy97 said:
oh..ok i didn't know this. Thanls for the information
I actually followed the steps.
fastboot devices -> then flash the vbmeta -> then flash TWRP -> but then i cannot switch to the Recovery anymore.
Booting the phone works fine but i cannot access the recovery anymore and it always directly jumps me back to fastboot mode. I followed several videos and tutorials here but whatever i do what works for others seems to not work for me
Whenever i try it seems like the recovery is gone. Even stock recovery is not accessable anymore. I wonder what i did wrong or if i need to flash other files too.
Click to expand...
Click to collapse
Assuming you've already unlocked bootloader and have all the mediatek drivers and ADB tools installed on your computer; Simply retry flashing vbmeta with the disable verity flag, then reflash twrp, and then reboot into recovery.
Make sure you've got a copy of the vbmeta.img and TWRP.img downloaded and place them in your ADB platform tools folder. Then run these commands
Make sure you shift-right click (for windows) on empty space in your platform tools folder and open powershel or command prompt (this is important), then send the following commands
Code:
fastboot devices
and wait for a response from your device to ensure it's connected
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then
Code:
fastboot flash recovery [YourTWRPfileName]
eg my twrp file name is TWRPopn2.img so i type "fastboot flash recovery twrpopn2.img"
then
Code:
fastboot reboot recovery
Make sure your ADB terminal and phone both say the flash was succesful after each flash. If not, then you likely didn't flash the partition at all.
My guess is likely that you shift-right clicked to open the powershell window in the wrong folder, such as your desktop, in which case sending the flash commands cann't find the right file to flash? Just a theory. Definitely sounds like your recovery partition got wiped though. You could also try redownloading TWRP to make sure you're using the right version of it.
Zombnombs said:
Assuming you've already unlocked bootloader and have all the mediatek drivers and ADB tools installed on your computer; Simply retry flashing vbmeta with the disable verity flag, then reflash twrp, and then reboot into recovery.
Make sure you've got a copy of the vbmeta.img and TWRP.img downloaded and place them in your ADB platform tools folder. Then run these commands
Make sure you shift-right click (for windows) on empty space in your platform tools folder and open powershel or command prompt (this is important), then send the following commands
Code:
fastboot devices
and wait for a response from your device to ensure it's connected
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then
Code:
fastboot flash recovery [YourTWRPfileName]
eg my twrp file name is TWRPopn2.img so i type "fastboot flash recovery twrpopn2.img"
then
Code:
fastboot reboot recovery
Make sure your ADB terminal and phone both say the flash was succesful after each flash. If not, then you likely didn't flash the partition at all.
My guess is likely that you shift-right clicked to open the powershell window in the wrong folder, such as your desktop, in which case sending the flash commands cann't find the right file to flash? Just a theory. Definitely sounds like your recovery partition got wiped though. You could also try redownloading TWRP to make sure you're using the right version of it.
Click to expand...
Click to collapse
Thanks for your help. I will try that again later.
What i can say i 100% opened the command prompt in the correct folder and the flash always said succesful.
I also thought about the command promt folder error before but it is correct. At least somehting got wiped (my recovery) but i simply cannot access it.
I will try again later and go over each step step by step and share ym results here. I hope i did a mistake because otherwise i don't know how to locate the problem.
Okey i did it again like the tutorial and also a second time like you said but it sadly didn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is my output from the command line. i use minimal ADB and fasstboot. But normal powershell by shift right click gives me the same output.
But when i try to reboot and boot into the recovery it just jumps to fastboot mode. So the stock recovery got flashed or removed then. But why i cannot boot into twrp?
Bootloader unlocked and based on the messages in the cmd everything fine.
Any ideas?
***Edit***
It worked now. If you ask me why, i don't know.
I did exactly the same in minimal adb and fastboot tools and on powershell. Both didn't work.
I did it in total 5 times and the last one in powershell randomly was succesful lol.
weird...
looks like the issue is more likely to do with your method of rebooting into recovery, as your reboot command did not seem to work.
Could be an issue with MinimalADB, or many other factors. If you're using the power button and volume keys combination, make sure you do it with your phone unplugged, as with the phone plugged in the combination boots to fastboot instead of recovery.
Zombnombs said:
looks like the issue is more likely to do with your method of rebooting into recovery, as your reboot command did not seem to work.
Could be an issue with MinimalADB, or many other factors. If you're using the power button and volume keys combination, make sure you do it with your phone unplugged, as with the phone plugged in the combination boots to fastboot instead of recovery.
Click to expand...
Click to collapse
Yeah might be true. I don't know.
Disclaimer: I am not responsible for bricked devices, dead SD cards, etc!
Warning: This procedure didn't work for some! Please test at your own risks!
Additional warning: do not relock your bootloader once your global rom is installed. You risk bricking your device.
1. Make sure your bootloader is unlocked
2. Download the images provided in the link below
3. Boot your device to recovery (hold volume up and power until reboot)
4. Wipe data
5. Boot your device to bootloader (hold volume down and power until reboot)
6. Connect your device to PC (make sure you have installed fastboot on your PC)
7. From windows command prompt cd into the folder containing the images
8. Install rooted or not boot image
Code:
fastboot flash boot boot.img
OR
Code:
fastboot flash boot boot_magisk.img
9. Run the following commands to flash all other images
Code:
fastboot flash dtbo dtbo.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash metadata metadata.img
fastboot flash oplusreserve2 oplusreserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash super super.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash userdata userdata.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
When flashing super.img, if you get the message Invalid sparse file format at header magic, this is fine.
9. You should then be able to boot into system
RMX3301 Stock files: https://drive.google.com/drive/folders/1-0pNU8DMhzQJjdIMYM_khqA5ASGqWatg
Mirror: https://mega.nz/folder/kw8w1QYR#Uro0gLle8Yr5uRZrqoyByg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anyone confirm this worked for them?
Great post. What is the Widevine level after installing the global rom? Furthrmore, does SafetyNet pass and do OTA updates work?
logmms said:
Great post. What is the Widevine level after installing the global rom? Furthrmore, does SafetyNet pass and do OTA updates work?
Click to expand...
Click to collapse
Google pay works, safetynet passes with Magisk module (probably good if you unroot and relock the bootloader but then you'll be stuck until realme unlocks the RMX3301).
but level 3 widevine unfortunately. Also some apps do detect that bootloader is unlock even with safetynet module.
Came here to say that this is working! Got my chinese version today and wanted to give it a try right away.
If this command takes a lot of time and seems like the console froze, don't panic!
Code:
fastboot flash vbmeta_vendor vbmeta_vendor.img
Almost every command took like 20 seconds, this one took almost 200, but it finishes eventually.
Also, you may end up stuck on a bootloop. But there's an easy fix, as myogui said on another thread:
Enter recovery mode, wipe data. Enter fastboot and then run the last 2 commands again:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
Now everything's working, and have been running the global rom all day flawlessly!
Does anyone know how to solve the bootloop problem? I tried the last 2 comands, Wipe Data, last 2 comands again... Flashing everything again... Nothing...
Any help would be very apreciate. Thanks.
UPDATE: It's working now.. lol... I tried flashing back to the Chinese version from myogui, still in bootloop.. Then I execute the comand "fastboot flash vbmeta vbmeta.img", bootloop... Then a tons of research... Then I downloaded a RMX3301 17.5GB .ofp file to try flashing from realme Flash Tool... Then I go to sleep... Then I woke up and just go to PC to fix this thing, but realme Tool didn't work, the Flash Tool said "CANNOT FIND CENTRAL DIRECTORY".... Then I just tried flashing here again with the files and comands above... what the hell, I'm screwed anyway... But this time worked.... LOL...
Big thanks guys!
Trying to lock again the bootloader... and then a message appears saying the flash was broken or something... now I can't even turn this thing off... Just keep flashing "realme Powered by android" screen rebooting again and again and again...
Oh my... to good to be true...
Tip: Just buy the global version.
No luck. Have tried all combinations of solutions and still stuck in bootloop. Have flashed it fresh 8 times and no luck. Also tried the last two commands above and no luck. And can't use OFP method as realme tool not updated for Gt 2 Pro
if you're stuck in bootloop try making sure you have the latest version of sdk platform tools, 33.0.1 worked for me.
try running the commands in this order
Code:
fastboot flash boot boot_magisk.img
fastboot flash dtbo dtbo.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash metadata metadata.img
fastboot flash oplusreserve2 oplusreserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash super super.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash userdata userdata.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
fastboot flash boot boot_magisk.img
then on your phone hit power button with start selected
Would relocking the bootloader after flashing the global brick me?
You would need to install Chinese rom again using another method of installation or wait for deep testing app to be available on global. But you could still use your device with the global version.
Bnblare said:
Would relocking the bootloader after flashing the global brick me?
Click to expand...
Click to collapse
Mine bricked, now it's hard brick... The closest that I got it to back to life was with QFIL, but something keep giving errors when I try to flash... Now I'm gonna try the MSM... If doesn't work maybe I'm gonna return the phone... Or wait until realme release a useful flash tool... Who knows...
I do not recomend locking back the phone based on my experience.
hacls said:
Mine bricked, now it's hard brick... The closest that I got it to back to life was with QFIL, but something keep giving errors when I try to flash... Now I'm gonna try the MSM... If doesn't work maybe I'm gonna return the phone... Or wait until realme release a useful flash tool... Who knows...
I do not recomend locking back the phone based on my experience.
Click to expand...
Click to collapse
Wow dude I'm sorry. Did you revert back to stock then try to relock the bootloader? Or did you try to relock while on the global?
myogui said:
You would need to install Chinese rom again using another method of installation or wait for deep testing app to be available on global. But you could still use your device with the global version.
Click to expand...
Click to collapse
Man.. I just wanna play call of duty again lol but it knows even tho my safetynet passes. the app can probably see it's L3 still. I guess I'll wait for realme to release the tool for this phone. I'm pretty sure flashing back to stock using the tool would safely lock the bootloader automatically
Bnblare said:
Wow dude I'm sorry. Did you revert back to stock then try to relock the bootloader? Or did you try to relock while on the global?
Click to expand...
Click to collapse
I tried to lock with the global ROM in it... Then this screen appears...
This photo are not mine, but it's the same screen... After that... Only in EDL mode...
hacls said:
I tried to lock with the global version... Then this screen appears...
View attachment 5591427
This photo are not mine, but it's the same screen... After that... Only in EDL mode...
Click to expand...
Click to collapse
your stuck with no fastboot and corrupted partitions. your gonna have to wait for someone to come out with a UnbrickMe zip or something. does adb recognize the phone?
hacls said:
I tried to lock with the global version... Then this screen appears...
View attachment 5591427
This photo are not mine, but it's the same screen... After that... Only in EDL mode...
Click to expand...
Click to collapse
Very sorry for you mate! I updated the OP to warn about this.
Bnblare said:
your stuck with no fastboot and corrupted partitions. your gonna have to wait for someone to come out with a UnbrickMe zip or something. does adb recognize the phone?
Click to expand...
Click to collapse
ADB doesn't recognize, like I said, for now on only in EDL mode.
Well, I gave up and paid a guy to flash via TeamViewer... And as I imagined... With MSM Download Tool was five clicks and it's done... Ridiculous easy... MSM would be a amazing tool if it were accessible... Unfreaking believable... Oh my...
But, anyway, it's solved. Thanks guys.