Related
Hello everyone,
I have an OG Pixel 5'', the stock Android was 7.1.2 and I updated it to Android 8.1 Oreo. Bootloader is unlocked, and I am able to install a TWRP 3.2.1-0 no problems. Phone at the time worked well. Now I have tried to flash an ElementalX Kernel on my device. This worked and I managed to boot. However, a message "There is an internal problem with your device, please contact the manufacturer". There is a thread to fix this and I should have done my research better.
Anyway, I went into TWRP and did a complete wipe of the phone, thinking that I could have just boot into TWRP again and copy the stock flashable zips to reflash the ROM.
It turns out that:
a) TWRP doesnt work. I.e when I got into fastboot mode (Power + Volume Down) and selected Recovery, the phone flashed to screen with Google image and then flashed back into the one with the green Android.
b) I managed to boot twrp via fastboot from my computer. So I booted into fastboot mode, and then on my computer, did: fastboot boot <twrp3.2.1.zip>. This worked and I managed to get into TWRP again. However, I cannot transfer file to flash. I.e when the phone showed up on my computer in TWRP, I cannot drag and drop anything into mounted folder.
I have tried the following to get stock ROM from this website: https://developers.google.com/android/images
a) I decided to look at ADB Sideload. So from the above website, I downloaded the zip files under Full OTA Images and then in TWRP, I went into Advance and chose ADB SIdeload. On my computer, I did "adb sideload name_of_zip_file_downloaded". The process started but ended very quickly, the finished time was 0.00 second, which means that nothing happened. Clearly, TWRP console showed that it is unable to mount /data and other folders. I guess the reason is that I am running a "live" TWRP? I checked by going back to TWRP mainscreen and tried to mount. However, all hard drives show 0MB (OTA USB and the main drive).
b) I used factory images approach by downloading zip from the same website, but this time under Factory Images. For this one, I unzip the files to a separate folder. Then I did flash-all.sh script but it said that my fastboot is too old.
So... to fix fastboot, I tried: (I am on Ubuntu 16.04.02)
a) Remove whole android fastboot with sudo apt-get remove, then reinstalled => Did not work. Still fastboot is too old
b) Download entire Android SDK from here: https://developer.android.com/studio/install.html. Fastboot still didnt work
c) From the Android Studio website, I tried to download just the command line tools. However, I could not find the folder with fastboot in it. A Google search shows that the fastboot and adb should be in platform-tools folder. Couldnt find any
Once again, I apologize for a very very long thread (It's 5am and I am trying to figure this thing out). Please, let me know if you guys can offer any help. Any help is greatly appreciated. FYI, I am coming from a Moto Z Play, and if things happen I would just boot into TWRP and copy the zip over. Clearly, this is not the case. This is my 1st Pixel as well.
Please let me know and thank you very very much.
Installing ex messes with the boot.IMG you need to reflash twrp after. Also don't manually flash stock zips that doesn't even make any sense. Download the latest android sdk or base platform tools then get the latest factory image and extract it into platform tools. Then go into fastboot and manually flash the official factory image
To use fastboot on ubuntu you have to put sudo infront of the command: sudo fastboot ........, Because of a permissions thing.
Sent from my Google Pixel using XDA Labs
Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel
maxwell0312 said:
Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel
Click to expand...
Click to collapse
I personally recommend using a custom kernel just make sure to follow the OP exactly. As the kernel and twrp are usually stored in the boot.img together and the kernel overwrites the boot.img the problem was likely that you just did things in the wrong order which would cause twrp to be removed. Typically the order of installing custom stuff from stock goes this way: flash_all to restore stock boot.img, boot twrp, factory wipe, flash rom, flash twrp, boot rom, reboot into recovery, flash kernel, flash twrp, reboot system, reboot recovery, flash magisk. Some rooms vary as they may require you to do things like flash a vendor img or delete the vendor overlay folder(always follow OP).
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Thank you, the tool worked like a charm.
BTW: I did search and find other "methods" but none of them worked
noncomjd said:
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
Click to expand...
Click to collapse
What you should have done was fastboot boot twrp.img. which would start twrp, then you could have used the installer in to install twrp on phone. After that you would have to installed stock or custom kernel.
MrSteelX said:
What you should have done was fastboot boot twrp.img. which would start twrp, then you could have used the installer in to install twrp on phone. After that you would have to installed stock or custom kernel.
Click to expand...
Click to collapse
That is exactly what I wanted to do.
I could get into TWRP, but I couldn't see the phone on the PC and couldn't move files (ROM) to the phone (although fastboot was working and I could see the device using adb) but I couldn't figure out how to have TWRP look for or find the ROM on the PC.
There's no recovery partition on A/B phones remember.
RusherDude said:
There's no recovery partition on A/B phones remember.
Click to expand...
Click to collapse
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
noncomjd said:
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
Click to expand...
Click to collapse
In twrp, you go to advance/sideload. Twrp then waits for adb sideload to push file to phone then auto flashes file.
In your case, you would sideload rom to flash and have been go to go.
noncomjd said:
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
Click to expand...
Click to collapse
If you have working fastboot mode and getting detected via fastboot then
fastboot flashable stock rom via fastboot mode.
U don't have to do anything just downloaded zip file unzip it any folder u want. Connect u r phone to. Computer in fastboot mode
Then go to that folder and just click flash all bat waut for 10to 15 min and then phone boots in working oos.
(all data will be get wipes after this)
Link
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/
MrSteelX said:
In twrp, you go to advance/sideload. Twrp then waits for adb sideload to push file to phone then auto flashes file.
In your case, you would sideload rom to flash and have been go to go.
Click to expand...
Click to collapse
Thanks.
I will give this a try. After I learn a little more about the A/B partitions & recovery on this phone, I want to try one on the custom ROMs.
pankspoo said:
If you have working fastboot mode and getting detected via fastboot then
fastboot flashable stock rom via fastboot mode.
U don't have to do anything just downloaded zip file unzip it any folder u want. Connect u r phone to. Computer in fastboot mode
Then go to that folder and just click flash all bat waut for 10to 15 min and then phone boots in working oos.
(all data will be get wipes after this)
Link
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/
Click to expand...
Click to collapse
Thanks for the link/guide. I had been trying an iteration of this (and the guide) but after reading your link, it too explains some things. I was trying to restore a Stock ROM from fastboot according to your link:
Things are changing with the advent of project treble. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlcoked. This will erase all your data and will wipe
I download and was trying to use the stock ROMs, I didn't see any bats, and now I know why.
Lots more reading to do. I love doing playing with this stuff, but trying to learn & keep up with things burns time, which most days I don't have.
This is the longest I've ever been on a stock OS (6 weeks? got the phone right after its release) although it's rooted (can never leave things completely alone).
noncomjd said:
Thanks for the link/guide. I had been trying an iteration of this (and the guide) but after reading your link, it too explains some things. I was trying to restore a Stock ROM from fastboot according to your link:
Things are changing with the advent of project treble. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlcoked. This will erase all your data and will wipe
I download and was trying to use the stock ROMs, I didn't see any bats, and now I know why.
Lots more reading to do. I love doing playing with this stuff, but trying to learn & keep up with things burns time, which most days I don't have.
This is the longest I've ever been on a stock OS (6 weeks? got the phone right after its release) although it's rooted (can never leave things completely alone).
Click to expand...
Click to collapse
I have to unzip the downloaded fastboot ROM at any folder on computer and open that folder u will see named [flash all bat]
Now connect phone in fastboot mode to computer and just click [flash all bat] file
noncomjd said:
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
Click to expand...
Click to collapse
"recovery" (what's left of it... wipe and mostly nothing else) is inside the boot partition. TWRP on those devices is installed into the boot partition (NOT overwriting the boot partition, but into the "ramdisk", a part of the kernel where OEM recovery resides and where TWRP, Magisk, Xposed and all the mods do their stuff on the kernel. On a phone with A/B partitions, you have to fastboot BOOT twrp, and then you have to flash the installer zip, you should never ever flash the image to any partition since there isn't any.
RusherDude said:
"recovery" (what's left of it... wipe and mostly nothing else) is inside the boot partition. TWRP on those devices is installed into the boot partition (NOT overwriting the boot partition, but into the "ramdisk", a part of the kernel where OEM recovery resides and where TWRP, Magisk, Xposed and all the mods do their stuff on the kernel. On a phone with A/B partitions, you have to fastboot BOOT twrp, and then you have to flash the installer zip, you should never ever flash the image to any partition since there isn't any.
Click to expand...
Click to collapse
Thanks for the information.
and this is what I did, originally I thought I had accidentally selected the wrong partition, but it seems since there is no recovery partition, I did it wrong from the start.
Q: I'm guessing this is why when you do load TWRP (the correct way, which I did once, following a guide) without a custom ROM (still using Oxygen OS) that the OEM recovery overwrites TWRP or the OEM recovery is called up at the next reboot into recovery?
Q: I understand, at least in theory the benefit of the A/B partitions, what is the benefit of eliminating the recovery partition other than giving more control of the phone to the OEM and OS? Is this setup limited to the stock kernel or mandated to be copied by any potential replacement kernels (this information is new to me, I haven't yet read up on kernels).
I'll start by apologizing if this has been solved elsewhere I have searched but found no answers.
I have the global variant and was rooted with twrp. I wanted the ota update so I unrooted and updated. Today I had some time so I flashed twrp wiped and entered bootloop. I attempted a full factory reset through twrp but still bootlooped. I have fastboot rom and have attempted to use miflash to fix it but get the "cannot found lock.bat" error though when first starting miflash I get the "can't find flash script" error. The drivers are properly installed yet the error persists. I cannot get adb to sideload which is, I'm guessing because of the wipe removing debugging mode? Is there any way to get the ROM image to the phone(I tried adb push command but says no device. Yet flashing recovery works so I know it's connected and recognized) so I can flash it via TWRP or the stock recovery img to flash and work from there? I'm kind of at a loss here. Am I now the proud owner of a very neat paper weight? I seriously hope not as I'm not exactly made of money and I've only owned the phone for a couple months.
Any and all help is greatly appreciated.
Update
I have managed to get adb push to start sending global v10.2.2.0 to the root folder. I'm hoping this will allow me to flash from twrp.
Mota420 said:
I'll start by apologizing if this has been solved elsewhere I have searched but found no answers.
I have the global variant and was rooted with twrp. I wanted the ota update so I unrooted and updated. Today I had some time so I flashed twrp wiped and entered bootloop. I attempted a full factory reset through twrp but still bootlooped. I have fastboot rom and have attempted to use miflash to fix it but get the "cannot found lock.bat" error though when first starting miflash I get the "can't find flash script" error. The drivers are properly installed yet the error persists. I cannot get adb to sideload which is, I'm guessing because of the wipe removing debugging mode? Is there any way to get the ROM image to the phone(I tried adb push command but says no device. Yet flashing recovery works so I know it's connected and recognized) so I can flash it via TWRP or the stock recovery img to flash and work from there? I'm kind of at a loss here. Am I now the proud owner of a very neat paper weight? I seriously hope not as I'm not exactly made of money and I've only owned the phone for a couple months.
Any and all help is greatly appreciated.
Click to expand...
Click to collapse
Update 2 phone working but still confused.
Pushing the ROM via ADB did indeed allow me to flash from twrp and restore the phone. My question now is why did it happen? Is the new OTA MIUI 10.3... update incompatible with twrp or did something anomalous happen with the flash? I flashed exactly the same method I used with the 10.2.2 ROM a few weeks ago....
OTA's should only be used when completely stock! Even though you uninstalled root, there were still system modifications that more than likely caused your issues. The fastboot version of the firmware is different than the TWRP image. You can not flash a TWRP image via fastboot, hence the missing scripts and bat files. If you had actually downloaded the fastboot image, you would have had a flash_all.bat file that would have returned your device completely to stock with a single run of that file.
Thanks for the reply and information. I actually expected my issues to begin upon installing the ota update and was quite surprised that it updated without error. What confuses me is how flashing twrp after the update caused the issues. I went through the normal process when flashing twrp and still ended up bootlooped. I made the mistake of thinking boot.img was the old stock recovery i renamed when i first rooted and flashing that as recovery. Obviously this was not the recovery file but fastboot. It was then that panic mode kicked in and things went from bad to worse. I formatted planning to flash the stock rom via adb which didn't work. Given that I never touched the fastboot image on the phone I'm confused on how the bat files and scripts weren't found.
I'll admit I'm not extremely well versed in this area.
Is it possible that the ota update contained different bat files and scripts than the previous rom had? Which would cause miflash to not recognize them when attempting to flash an older rom? I'm sorry if my questions are ignorant lol. I'm a process guy and a troubleshooter by nature which means even though I've resolved the issue, I need to figure out what caused it.
Would flashing fastboot to the phone as the recovery image have screwed up the bat and scripts? Having two instances of boot.img on the partition messed it up maybe? Was it the formatting even though I was still able to boot into fastboot after? Or was it something that happened during the unrooting and updating that messed it up and it didn't manifest until I flashed twrp? Like I said the update worked fine and the phone was fully functional until I tried to reroot.
Thanks again for taking the time to help. It's definitely appreciated.
Mota420 said:
Thanks for the reply and information. I actually expected my issues to begin upon installing the ota update and was quite surprised that it updated without error. What confuses me is how flashing twrp after the update caused the issues. I went through the normal process when flashing twrp and still ended up bootlooped. I made the mistake of thinking boot.img was the old stock recovery i renamed when i first rooted and flashing that as recovery. Obviously this was not the recovery file but fastboot. It was then that panic mode kicked in and things went from bad to worse. I formatted planning to flash the stock rom via adb which didn't work. Given that I never touched the fastboot image on the phone I'm confused on how the bat files and scripts weren't found.
I'll admit I'm not extremely well versed in this area.
Is it possible that the ota update contained different bat files and scripts than the previous rom had? Which would cause miflash to not recognize them when attempting to flash an older rom? I'm sorry if my questions are ignorant lol. I'm a process guy and a troubleshooter by nature which means even though I've resolved the issue, I need to figure out what caused it.
Would flashing fastboot to the phone as the recovery image have screwed up the bat and scripts? Having two instances of boot.img on the partition messed it up maybe? Was it the formatting even though I was still able to boot into fastboot after? Or was it something that happened during the unrooting and updating that messed it up and it didn't manifest until I flashed twrp? Like I said the update worked fine and the phone was fully functional until I tried to reroot.
Thanks again for taking the time to help. It's definitely appreciated.
Click to expand...
Click to collapse
OTA's are not a complete image. It is a partial update that only replaces what it has to replace. If MiFlash dis not recognize the image, it was either the wrong image or a corrupt image.
Sometimes updates to the system and recovery partitions fix exploits that things like root and TWRP take advantage of.
Fastboot isn't something you flash to the phone. It is a command line used to flash a dull factory image to the device properly. You do not need MiFlash to flash a fastboot factory image. All you do is extract the full image to your ADB folder unless it is system wide, boot your device into the bootloader, connect ir to your PC, and run the flash_all.bat command contained in the folder you extracted. A command prompt window will open, everything will complete after about a few minutes the window will close, and your phone will reboot.
So the "fastboot" rom is a rom designed to be flashed using fastboot? The miflash error was given because the rom I was trying to flash was corrupted. That makes sense as I'd never known of a fastboot rom before. But it has been a few years since I rooted and romd my phone. I always did the typical flash from the rom image from twrp. I'm still not sure how I got myself in a boot loop unless when I wiped after flashing twrp I accidentally selected another option that erased more than I wanted.. Which makes perfect sense. I knew it had to be an ID10T error lol.
Thanks for the explanation.
So I was trying to install a custom ROM (first time ) did unlock my bootloader and when wiped using twrp and then rebooted to twrp for flashing the ROM it said that system has been destroyed when I tried to reboot to recovery then also it was of no use.I tried to flash fastboot roms via miflash tool. The new versions couldnt find scripts o don't know why so I tried the old ones but the flash got completed in 1 second so it was useless.further more I think that I have anti rollback v2 in my phone and that's why I'm not able to go anywhere..
Is there any fix please help
Try to manual flash using fastboot
Fastboot flash system system.img
Fastboot flash recovery recovery.img
Then flash EU rom
LovingDracula04 said:
So I was trying to install a custom ROM (first time ) did unlock my bootloader and when wiped using twrp and then rebooted to twrp for flashing the ROM it said that system has been destroyed when I tried to reboot to recovery then also it was of no use.I tried to flash fastboot roms via miflash tool. The new versions couldnt find scripts o don't know why so I tried the old ones but the flash got completed in 1 second so it was useless.further more I think that I have anti rollback v2 in my phone and that's why I'm not able to go anywhere..
Is there any fix please help
Click to expand...
Click to collapse
The same thing happened to me when I tried to install and use TWRP.
To fix this, I used the MiFlash tool and flashed the fastboot ROM which you can download from here.
LovingDracula04 said:
So I was trying to install a custom ROM (first time ) did unlock my bootloader and when wiped using twrp and then rebooted to twrp for flashing the ROM it said that system has been destroyed when I tried to reboot to recovery then also it was of no use.I tried to flash fastboot roms via miflash tool. The new versions couldnt find scripts o don't know why so I tried the old ones but the flash got completed in 1 second so it was useless.further more I think that I have anti rollback v2 in my phone and that's why I'm not able to go anywhere..
Is there any fix please help
Click to expand...
Click to collapse
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
try unlock bootloader via internet
format data once via twrp
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!