Related
Help ! Help ! Help !
First of all My power key is not working
I was using stock rom 5.1 in my Moto G falcon xt1033 and was so curious about android M and CM13 . So I installed Teamwin TWRP recovery and flashed Official Cyanogenmod 13 (nightly) with nexus 4 gaaps.
It was running smooth then i installed Cosmos CM12.X theme from CM Theme after upadate of theme i got msg " Unfortunately, System UI has stopped. "
Due to not working of my power button i used google device manager to restart phone by choosing Erase my phone .
then my phone is gone to bootloop. Now i can see only Flashing screen of " teamwin '.
Please help me . How to fix it?
Thanks in advance.
You need to get fastboot / ADB working on a PC / Laptop. See FAQ Question 6: http://forum.xda-developers.com/showthread.php?t=2537119
The following command will get TWRP Recovery working:
fastboot erase userdata
When in TWRP Recovery, you can push a ROM.zip to phone using this command:
adb push ROM.zip /sdcard/
lost101 said:
You need to get fastboot / ADB working on a PC / Laptop. See FAQ Question 6: http://forum.xda-developers.com/showthread.php?t=2537119
The following command will get TWRP Recovery working:
fastboot erase userdata
When in TWRP Recovery, you can push a ROM.zip to phone using this command:
adb push ROM.zip /sdcard/
Click to expand...
Click to collapse
on my moto g xt1033,
after, installing ROM CM-13.0-20160820-SNAPSHOT-ZNH5YAO0J1-falcon
Then i, installed Gapps = ARM_6.0_micro (opengapps.org)
then everything is fine play games, etc.
i installed super su from play store, but unable to update binary!
so boot into recovery and flash UPDATE-SuperSU-v2.46.zip
now i stuck in boot loop,
(Earlier Point)now what to do?> and after installation of rom twrp asking me for partition modification- Keep Read-Only OR Allow Modification. i select allow modification. so where i go wrong?
NOw stuck in boot loop, i can able to in Fastboot and select recovery also,
so what do i do, option 1-> wipe everything n install rom , gapps again.
option2-> without wiping install rom (like doing overwrite) onalready installed rom.
@Nile786 - Might be worth flashing a more recent version of SuperSU: https://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
@lost101
Thanks for Ur help, that SuperSU zip file, I flashed in twrp, it really worked for me.:good:
How to revert back to normal from gpe... Urgent help plz
Sent from my Redmi 3S using XDA-Developers mobile app
Hi,
as I did not find an English guide for rooting a BQ Aquaris M10 tablet and had some problems when trying to root my tablet, I want to post an guide how to root this tablet.
First of all:
- This guide is just from my experience and is not thoroughly tested. It's on your own if you risk bricking your device.
- If you get stuck in the process, in nearly all cases you can revert to stock with the MTK flash tool (can be found on mibqyyo.com) and the images provided by BQ on their website.
- I could not unlock the bootloader with the 1.X-Images (Lollipop), as the VolumeUp-Button didn't work in fastboot-mode and you need this button to confirm the unlock.
- Booting into recovery from start with VolumeUp and Power-Button. This doesn't work with the 1.X-images, too.
- This guide is not intended for users without experience in unlocking/rooting a device. If you don't know how to use adb, fastboot, recovery and things like that, don't try it!
- You will loose all your data during this process!!
Guide:
Modify boot.img, flash new firmware
SuperSU in systemless mode doesn't work on stock image, as the SuperSU installer can't extract boot.img. You have to repack boot.img.
I tried a SuperSU installer without systemless-mode, but device didn't even boot anymore afterwards.
This guide is derived from a Spanish tutorial on the HTCmania-forum ("Root M10 HD Marshmallow") by yquepongo. Thanks to him!
Get a firmware for your device from the BQ-website (should be Marshmallow, see above) and unzip it to a directory.
Extract the boot-verified.img in the firmware directory with a bootimg-extractor. There are various tools available.
I used bootimg.exe, because this was explained in the mentioned thread and I even used it with wine on Linux and it went well.
Search for cpiolist.txt in your extracted boot-verified.img and delete the first two lines:
mode:mtk
mtk_header_name:ROOTFS
Repack boot-verified.img and put it back in the firmware directory.
Flash the modified firmware with the MTK flash tool according to the tutorial on .mibqyyo.com (Title "Hard Reset for the smartphone range Aquaris and Aquaris E"). In short: Disconnect device, start Tool, load scatter file from firmware directory, choose firmware upgrade, start download, connect the device in power off state, download will start automatically.
This will delete all your data and put the device back to factory rom (hard reset)!!!
If you don't want to flash the complete firmware, you can flash only the boot-verified.img with "Download only" in the flash tool. I didn't try this and don't know if this is working.
Start your device, don't activate any security settings to prevent encryption of data partition.
Unlock bootloader, flash TWRP, install SuperSU
Enable developer settings on device and activate "OEM unlock" in developer settings.
Reboot into fastboot (adb reboot bootloader) and unlock bootloader (fastboot oem-unlock).
This will delete all your data!!! Reboot your system afterwards to make sure everything is still ok.
Do not activate any security settings and make sure your data partition is not encrypted!
The existing TWRP-image can't handle an encrypted data partition, you will end in a boot loop and have to start the whole process again!
Double check, your data partition isn't encrypted. (Settings - Security)
Reboot into fastboot (adb reboot bootloader) and flash the TWRP-image from the TWRP-site (fastboot flash recovery twrpxxx.img)
After reboot TWRP should start.
If you have checked that everything is ok (I would recommend a reboot into normal mode), you can install SuperSU with the standard-installer-zip in TWRP.
If you didn't modify your boot.img, the installer will give a warning that it cannot extract boot.img and you will not find any SuperSU on your system.
If you get stuck in bootloop afterwards you can start anew and try it with another image flashed with MTK flash tool. (Firmware 2.2.0 from December 2016 for freezerhd worked in my case)
Maybe some steps could be shortened, but I haven't tried it.
hi zrfl,
i have a bq aquarius m8 with mm os.
the m8 has the same resolution (1280x800)
can i try the twrp recovery from the m10?
i will also root my m8 but i cant extract the boot-sign.img.
all tools fails.
have you any ideas?
update:
yesterday i opened the bootloader. the volume button works in fastboot-mode.
also i can unlock the boot image with the tools from: https://forum.xda-developers.com/showthread.php?t=2073775
but the unpack fails:
Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers
Supplied image: unlokied-new.img
Setting up work folders . . .
Splitting image to "/split_img/" . . .
Android boot magic not found.
Error!. . .
Click to expand...
Click to collapse
i think this bq boot image use non-standard header. any ideas how to root this bq aquarius m8?
i buyed this tablet only to can use xposed.
i think, any android without root or xposed is useless
i opened a separate theme for this : https://forum.xda-developers.com/android/general/root-help-to-root-twrp-recovery-bq-t3536170
dreas74 said:
hi zrfl,
i have a bq aquarius m8 with mm os.
the m8 has the same resolution (1280x800)
can i try the twrp recovery from the m10?
i will also root my m8 but i cant extract the boot-sign.img.
all tools fails.
have you any ideas?
update:
yesterday i opened the bootloader. the volume button works in fastboot-mode.
also i can unlock the boot image with the tools from: https://forum.xda-developers.com/showthread.php?t=2073775
but the unpack fails:
i think this bq boot image use non-standard header. any ideas how to root this bq aquarius m8?
i buyed this tablet only to can use xposed.
i think, any android without root or xposed is useless
Click to expand...
Click to collapse
Sorry, but I can't help you there, as the M8 seems to be too different to the M10: I didn't have to unlock the boot.img, it was easy to unpack.
hi zrfl,
thanks for your reply. i contacted the developer osmOsis from the android image kitchen.
he will implement the bq specials in his tools.
more in the AIK thread: https://forum.xda-developers.com/showthread.php?t=2073775&page=108
this is the only way to root this device !!
thanks a lot ...
Thanks for this tutorial.
I've followed all the step, I'm able to flash the new recovery from the TWRP website but then I do a
Code:
fastboot reboot-bootloader
but the device reboot normally, just with a warning message during boot saying something like "This device is unlock and can't be trusted, it will boot in 5 seconds".
So I'm unable to access TWRP recovery, I guess when the device reboot it override the recovery partition because if I do a
Code:
adb reboot recovery
I end up in the Android recovery not TWRP.
Any idea ?
Thanks
ZazOufUmI said:
Thanks for this tutorial.
I've followed all the step, I'm able to flash the new recovery from the TWRP website but then I do a
Code:
fastboot reboot-bootloader
but the device reboot normally, just with a warning message during boot saying something like "This device is unlock and can't be trusted, it will boot in 5 seconds".
So I'm unable to access TWRP recovery, I guess when the device reboot it override the recovery partition because if I do a
Code:
adb reboot recovery
I end up in the Android recovery not TWRP.
Any idea ?
Thanks
Click to expand...
Click to collapse
Sorry, I have done this a long time ago and don't know what could be wrong:
You have the correct message, so unlock was successfull
You try to reboot in fastboot, so you flashed TWRP correctly in fastboot-mode
And I don't have the device at hand to try it myself. But I do have a few suggestions, what you could try:
Don't try to shorten procedure with unlock and flashing of TWRP at once. I'm not sure, but I think I had problems when I tried this. So do a normal reboot after unlock, before booting again into fastboot and flashing TWRP. (Now you have done this already )
I don't remember the proper boot command after flashing of TWRP. But
Code:
fastboot reboot-bootloader
doesn't make sense: You are already in bootloader.
Is there a boot-option in the bootloader where you could choose recovery?
Otherwise better power off and use the key-combination for booting into recovery: VolumeUp+Power.
I think, you have to repeat the procedure, as recovery seems to be overwritten: Boot into fastboot, flash TWRP, reboot into recovery. And avoid normal booting before first boot into TWRP!
Did you use the newest TWRP 3.1.0 from March 8th? I haven't tried this yet, so there could be the problem. You could try the previous one: 3.0.2 from last year.
Thanks, I succeed with the combo key (power + vol up) directly after the reboot process
Perfect it's working great now !
I did exactly what you wrote but SuperSU won't install because it cannot extract the ramdisk...
Hi @zrfl
Thanks for your posting!
I did as you suggested and successfully unlocked bootloader and installed TWRP 3.1.1. Your hint to modify the boot-verified was extremely helpful, as I wouldn't be able to unlock the bootloader otherwise.
However, I did not manage to install super su. And boy, I tried many different versions od regular/system/systemless supersu, each flashed according to the respective how-to.
I ended up either in a bootloop, or get stuck on the Android logo at boot.
Flashing goes well until this step:
"Decompressing ramdisk
--- Failure, aborting"
I checked ramdisk compression of boot with Carliv image Kitchen and it tells me that it already is set to "gz" and not another compression TWRP can't handle.
Please help me on how to flash SuperSu.
Thanks and best
Tom
There is something wrong: TWRP does not need a modified boot.img.
Maybe newer ROM-versions are different.
Solution for geting root on BQ M10 FHD on stock rom 2.6.2: Start with a fresh system and install magisk beta (not stable), reboot and root is granted!
tanks a lot to @scafroglia93!
Are there any Custom ROM's
For this Tablet like CM/LineageOS AOSP etc?
Googling reveals nothing and Considering all the kernel mods like hardcore and Ubuntu touch I find it hard to believe that nobody has built one of the later.
I've been searching for custom ROMs too. Apparently, there are none available at present. However, I'd highly appreciate lineage rom.
https://www.xda-developers.com/motorola-one-power-moto-z3-play-twrp/
Support Status: Current
Maintainer: kaneawk, erfanoabdi
Code Name: beckham
Device Tree / files
NOTE: Monthly security updates may break
decryption of /data in TWRP. MTP does not
work at this time, but you can use adb to transfer files.
Click to expand...
Click to collapse
https://twrp.me/motorola/motorolamotoz3play.html
The new twrp works fine
Hopefully this means more support in the future. Did you flash or boot? Curious if it will bootloop if I flash the img
Installation:
If you do not already have TWRP installed: Download twrp img. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot twrp.img
This will temporarily boot TWRP on your device.
I'm aware of how to boot TWRP on my device. I was wondering if it would be possible to *flash* it though. As I understand it you need the TWRP zip compiled and was wondering if you got that working or not for this device.
Booting is fine for now but I need to have TWRP as recovery for bootloops when I don't have my PC available
Edit for spelling
what works
I have downloaded the twrp.img
I ran fastboot boot twrp.img
I have downloaded magisk 17.1 and flashed it via twrp
Installed Magisk Modules: AdgaurdDNS, Greenify4Magisk, and Viper4Android FX
what doesn't work
installed xposed framework via magisk -> caused bootloop
Pretty sure it's an Xposed bug because Xposed bootloops on any device that's got 8.1 with latest patches
So if we can unlock the bootloader, and boot to twrp, can we not install supersu from there? Or am I understanding this wrong?
Magisk is superior in about every way. Also super su isn't being developed anymore
Ah, I'll look into it more. My last phone was forever old, and my only option was SuperSU. Thanks!
please any help update the download TWRP file, because in github the developers say mount vendor is working, but the file in twrp webpage its old.
Has anyone tried booting this on the Sprint version
Help me plz
hello, Im trying to install the twrp recovery but i cant, its happing a error
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.999s
and i dont know how to solve, please help me
Trwp can't be installed on this device as far as I know. Available twrp is for booting purposes only.
Fastboot boot twrp.img
Click to expand...
Click to collapse
Whenever I use the command fastboot boot twrp.img, it boots just fine but if I try to use fastboot flash recovery twrp.img, it gives me an invalid partition name recovery error. I am trying to root the device. To my understanding, if you just boot into TWP, its only temporary. I guess my question is, is flashing the .img necessary and if so, why is it giving me this error? I got the .img from the offical website, its in the same folder as fastboot, and even boots right up if using the boot command so the image isnt corrupt. Any suggestions?
You don't need twrp for root. Boot the image and use magisk to root your device systemlessly. SuperSU is depreciated. And twrp hasn't been built for this device in a flashable format. You can only boot temporarily and install magisk.
?
darkdaemon32 said:
You don't need twrp for root. Boot the image and use magisk to root your device systemlessly. SuperSU is depreciated. And twrp hasn't been built for this device in a flashable format. You can only boot temporarily and install magisk.
Click to expand...
Click to collapse
So can I root this device without installing TWRP? I want to continue using my mods (which I believe TWRP will break) and I don't really care about the custom recovery at this point but want root access for a few select items like AdAway.
There isn't even a way to currently INSTALL TWRP on the z3. The only way to use twrp is with fastboot boot. And you use this to temporarily boot to twrp and flash the magisk installer zip for root. Magisk is systemless and doesn't modify system so you should be able to use all apps that detect system modifications such as gpay etc.
Would anyone help me? I saved the Magisk file to internal memory, but when I try to install TWRP (fastboot boot twrp.img) the internal memory files are encrypted.
How do I decrypt these files so I can do the Root?
Hey guys, I bricked my Realme X50 Pro today and I'm a bit stuck trying to boot it again. It's the Spanish version, RMX2071.
I was able to install TWRP and flashed the stock ROM zip from there using adb push (I converted the ozip file to zip using ozipdecrypt). It says "successful" but it still doesn't work: after rebooting, stays stuck in the realme logo and after a few minutes goes into TWRP recovery mode.
I don't know what else to try. I don't care about the data, I just want the phone to work again. I don't know if the zip is the problem, but I can't flash the .ozip file using TWRP and can't find the stock recovery.img anywhere.
Thanks in advance.
*SOLVED:
Hi all! I managed to solve this issue and my X50 Pro is running normally now I'm posting here how I did it, so it can help anyone with the same problem:
1. My phone had TWRP recovery and you can't flash any Realme stock ROM from there, so I flashed the Indian ROM using the Realme Flash Tool. In this link you can find the tool and the .ofp file needed.
2. Now the phone was bootlooping, so we need to get the stock recovery. For that, you need to follow this tutorial (I used the .ozip file of the version I wanted, but I think it works with the .ozip of any version) to get generate the image files needed.
3. As you will see, the recovery.img doesn't exist in the final folders, but you can create it with some files you get in the 01-Project folder. To generate it, follow this. Basically, you need to get the boot.img and the file recovery-from-boot.p (located in /01-Project/vendor), copy them in the same folder, open the Linux shell in that folder and do:
Code:
bspatch boot.img selfmade_stock_recovery.img recovery-from-boot.p
(in case you are using Windows, you can install the Linux shell following this and then install bspatch following this steps).
4. Now that we have our stock recovery (selfmade_stock_recovery.img), we can flash it into our phone while in fastboot mode using the command line:
Code:
fastboot flash recovery selfmade_stock_recovery.img
5. In your mobile, go to stock recovery and Wipe Data and Format. When I did this, the device booted correctly in the Indian version I installed via .ofp file. If your phone doesn't boot correctly, you should be able to put the .ozip of the version you want in a flashdrive and use an OTG cable to flash it directly to the phone via stock recovery (Install via OTG).
6. If your device booted correctly, you can download your stock ROM .ozip file, put it in the internal storage of your phone and install it via stock recovery.
Thanks all, hope it helps
Deesubicado said:
Hey guys, I bricked my Realme X50 Pro today and I'm a bit stuck trying to boot it again. It's the Spanish version, RMX2071.
I was able to install TWRP and flashed the stock ROM zip from there using adb push (I converted the ozip file to zip using ozipdecrypt). It says "successful" but it still doesn't work: after rebooting, stays stuck in the realme logo and after a few minutes goes into TWRP recovery mode.
I don't know what else to try. I don't care about the data, I just want the phone to work again. I don't know if the zip is the problem, but I can't flash the .ozip file using TWRP and can't find the stock recovery.img anywhere.
Thanks in advance.
*UPDATE: I flashed the stock ROM ozip file using TWRP. Now I have a bootloop: it starts with the realme and android white logo, then goes to the realme orange logo, but in the end it restarts again and starts the loop again
Click to expand...
Click to collapse
Take a look what the user "pppwaung" has reported in 15th June 2020, 09:38 AM and confirm if it can help:
https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page4
can you share that stock recovery.img?
i tried to bspatch but get `bspatch: Corrupt patch`
ttongg said:
can you share that stock recovery.img?
i tried to bspatch but get `bspatch: Corrupt patch`
Click to expand...
Click to collapse
Same situation.... Seems my Ubuntu 20.04 has a little problem.
Wish someone could help to upload RMX2071 recovery img~~ will appreciate it so much.
Sincerely,
ttongg said:
can you share that stock recovery.img?
i tried to bspatch but get `bspatch: Corrupt patch`
Click to expand...
Click to collapse
93123211 said:
Same situation.... Seems my Ubuntu 20.04 has a little problem.
Wish someone could help to upload RMX2071 recovery img~~ will appreciate it so much.
Sincerely,
Click to expand...
Click to collapse
Here is the recovery.img I made for the RMX2076EU_11_A.20 version. Hope it helps
Deesubicado said:
Here is the recovery.img I made for the RMX2076EU_11_A.20 version. Hope it helps
Click to expand...
Click to collapse
Hello Mate,
Thanks for your so kindly help.
I figured out what caused the boot loop
After I flashed the EU or India version OZIP via TWRP, the data file became wrong and keep booting loop.
Then I have to flash this stock rom on my RM2071, and going to clear --> format data
After that it goes reboot automatically, than boot up in two minutes, asking me to select language~~
Thanks for your kindly help again~~
Deesubicado said:
Hey guys, I bricked my Realme X50 Pro today and I'm a bit stuck trying to boot it again. It's the Spanish version, RMX2071.
I was able to install TWRP and flashed the stock ROM zip from there using adb push (I converted the ozip file to zip using ozipdecrypt). It says "successful" but it still doesn't work: after rebooting, stays stuck in the realme logo and after a few minutes goes into TWRP recovery mode.
I don't know what else to try. I don't care about the data, I just want the phone to work again. I don't know if the zip is the problem, but I can't flash the .ozip file using TWRP and can't find the stock recovery.img anywhere.
Thanks in advance.
*SOLVED:
Hi all! I managed to solve this issue and my X50 Pro is running normally now I'm posting here how I did it, so it can help anyone with the same problem:
1. My phone had TWRP recovery and you can't flash any Realme stock ROM from there, so I flashed the Indian ROM using the Realme Flash Tool. In this link you can find the tool and the .ofp file needed.
2. Now the phone was bootlooping, so we need to get the stock recovery. For that, you need to follow this tutorial (I used the .ozip file of the version I wanted, but I think it works with the .ozip of any version) to get generate the image files needed.
3. As you will see, the recovery.img doesn't exist in the final folders, but you can create it with some files you get in the 01-Project folder. To generate it, follow this. Basically, you need to get the boot.img and the file recovery-from-boot.p (located in /01-Project/vendor), copy them in the same folder, open the Linux shell in that folder and do:
Code:
bspatch boot.img selfmade_stock_recovery.img recovery-from-boot.p
(in case you are using Windows, you can install the Linux shell following this and then install bspatch following this steps).
4. Now that we have our stock recovery (selfmade_stock_recovery.img), we can flash it into our phone while in fastboot mode using the command line:
Code:
fastboot flash recovery selfmade_stock_recovery.img
5. In your mobile, go to stock recovery and Wipe Data and Format. When I did this, the device booted correctly in the Indian version I installed via .ofp file. If your phone doesn't boot correctly, you should be able to put the .ozip of the version you want in a flashdrive and use an OTG cable to flash it directly to the phone via stock recovery (Install via OTG).
6. If your device booted correctly, you can download your stock ROM .ozip file, put it in the internal storage of your phone and install it via stock recovery.
Thanks all, hope it helps
Click to expand...
Click to collapse
Disculpa despues de lo que hiciste en que version se quedo cn o pu
RMX2071 is a CN version. So from CN version to Indian successful?
ENJOY
Just flash this boot.img and will work. Its extracted by me, i dont want other to struggle like i did.
I am new user, i cant post links, but PM me and maybe I can.
Deesubicado said:
Hey guys, I bricked my Realme X50 Pro today and I'm a bit stuck trying to boot it again. It's the Spanish version, RMX2071.
I was able to install TWRP and flashed the stock ROM zip from there using adb push (I converted the ozip file to zip using ozipdecrypt). It says "successful" but it still doesn't work: after rebooting, stays stuck in the realme logo and after a few minutes goes into TWRP recovery mode.
I don't know what else to try. I don't care about the data, I just want the phone to work again. I don't know if the zip is the problem, but I can't flash the .ozip file using TWRP and can't find the stock recovery.img anywhere.
Thanks in advance.
*SOLVED:
Hi all! I managed to solve this issue and my X50 Pro is running normally now I'm posting here how I did it, so it can help anyone with the same problem:
1. My phone had TWRP recovery and you can't flash any Realme stock ROM from there, so I flashed the Indian ROM using the Realme Flash Tool. In this link you can find the tool and the .ofp file needed.
2. Now the phone was bootlooping, so we need to get the stock recovery. For that, you need to follow this tutorial (I used the .ozip file of the version I wanted, but I think it works with the .ozip of any version) to get generate the image files needed.
3. As you will see, the recovery.img doesn't exist in the final folders, but you can create it with some files you get in the 01-Project folder. To generate it, follow this. Basically, you need to get the boot.img and the file recovery-from-boot.p (located in /01-Project/vendor), copy them in the same folder, open the Linux shell in that folder and do:
Code:
bspatch boot.img selfmade_stock_recovery.img recovery-from-boot.p
(in case you are using Windows, you can install the Linux shell following this and then install bspatch following this steps).
4. Now that we have our stock recovery (selfmade_stock_recovery.img), we can flash it into our phone while in fastboot mode using the command line:
Code:
fastboot flash recovery selfmade_stock_recovery.img
5. In your mobile, go to stock recovery and Wipe Data and Format. When I did this, the device booted correctly in the Indian version I installed via .ofp file. If your phone doesn't boot correctly, you should be able to put the .ozip of the version you want in a flashdrive and use an OTG cable to flash it directly to the phone via stock recovery (Install via OTG).
6. If your device booted correctly, you can download your stock ROM .ozip file, put it in the internal storage of your phone and install it via stock recovery.
Thanks all, hope it helps
Click to expand...
Click to collapse
Nothing different happened, the same things continue Fastboot stuck
smhzhl said:
Nothing different happened, the same things continue Fastboot stuck
Click to expand...
Click to collapse
same
Deesubicado said:
Hey guys, I bricked my Realme X50 Pro today and I'm a bit stuck trying to boot it again. It's the Spanish version, RMX2071.
I was able to install TWRP and flashed the stock ROM zip from there using adb push (I converted the ozip file to zip using ozipdecrypt). It says "successful" but it still doesn't work: after rebooting, stays stuck in the realme logo and after a few minutes goes into TWRP recovery mode.
I don't know what else to try. I don't care about the data, I just want the phone to work again. I don't know if the zip is the problem, but I can't flash the .ozip file using TWRP and can't find the stock recovery.img anywhere.
Thanks in advance.
*SOLVED:
Hi all! I managed to solve this issue and my X50 Pro is running normally now I'm posting here how I did it, so it can help anyone with the same problem:
1. My phone had TWRP recovery and you can't flash any Realme stock ROM from there, so I flashed the Indian ROM using the Realme Flash Tool. In this link you can find the tool and the .ofp file needed.
2. Now the phone was bootlooping, so we need to get the stock recovery. For that, you need to follow this tutorial (I used the .ozip file of the version I wanted, but I think it works with the .ozip of any version) to get generate the image files needed.
3. As you will see, the recovery.img doesn't exist in the final folders, but you can create it with some files you get in the 01-Project folder. To generate it, follow this. Basically, you need to get the boot.img and the file recovery-from-boot.p (located in /01-Project/vendor), copy them in the same folder, open the Linux shell in that folder and do:
Code:
bspatch boot.img selfmade_stock_recovery.img recovery-from-boot.p
(in case you are using Windows, you can install the Linux shell following this and then install bspatch following this steps).
4. Now that we have our stock recovery (selfmade_stock_recovery.img), we can flash it into our phone while in fastboot mode using the command line:
Code:
fastboot flash recovery selfmade_stock_recovery.img
5. In your mobile, go to stock recovery and Wipe Data and Format. When I did this, the device booted correctly in the Indian version I installed via .ofp file. If your phone doesn't boot correctly, you should be able to put the .ozip of the version you want in a flashdrive and use an OTG cable to flash it directly to the phone via stock recovery (Install via OTG).
6. If your device booted correctly, you can download your stock ROM .ozip file, put it in the internal storage of your phone and install it via stock recovery.
Thanks all, hope it helps
Click to expand...
Click to collapse
Brilliant mate, you are a lifesaver. thanks a ton!
Hi,
First of all, yes, I have checked the other threads that talk about reverting to stock and I am still stuck.
So I installed Kang OS which is Android 11, and now I want to revert to stock. I have tried downloading multiple different versions of the fastboot ROM from the page https://androidfilehost.com/?w=files&flid=294300 and run the flash all batch file and every time I am either getting stuck in a boot loop or getting the Verity Crash Dump Screen. I have managed to reach the fastboot screen, and I am waiting on the fastboot screen, for someone to show me some way.
Thanks in Advance.
If you used a pin then your storage is encrypted and the rom you are trying to flash can't use it, that's why you're most likely stuck at boot.
I ran into the same issue and posted about it in the same thread. I think we will need a new version of TWRP as 3.4.0-0 would not accept my pin which had not changed.
To fix your issue, sadly, you'll need to wipe your storage:
Boot the phone into fastboot mode
Attach your USB cable to the phone/PC
Download and unzip the file I've attached (ADB/Fastboot)
Launch an elevated command window in the folder you extracted the attached zip to
Try the command fastboot devices and ensure that it reports the device correctly, if not then you need to install the latest OnePlus drivers
Type the following in the command window : fastboot -w (This will wipe the storage)
Try your rom again (TWRP should remain as the recovery if you had flashed it already, if not then copy the latest TWRP img file to the same folder as the ADB/Fastboot tools, use fastboot and type boot twrpfilename.img this will make the phone boot into TWRP recovery, you can then copy over the TWRP zip and flash it to recovery using the booted version of TWRP)
Once you've done the above you shouldn't really need to use the fastboot scripts as the latest rom should just flash from TWRP.
Get msm download tool for guacamole which is the codename of the op7p. I know the shorts with the global version I am unsure if this works with T-Mobile or others?
MSM is a bit of a severe fix when they've already confirmed they can still get fastboot, MSM is for completely bricked phones that can't access anything. Wiping the storage and going to fastboot will allow them to just flash recovery then flash the stock rom. Way easier.
Boot into twrp. Then format data. Phone will boot then.