Question Need older stock CN ROM rollback - Realme GT

Hello,
I've been trying to instal non CN OS, as CN one is not working with Android Auto.
I can't find CN stock ROM older than A24, which is not working for me. Can someone upload older stock CN ROM for RMX2202, please? I've searched the entire forum, but found only A24.
Best Regards,
Browar9000

hoangzk9 said:
Hi, this what you need
┤Mod Edit├┤Link removed (untrustworthy publisher)├
Click to expand...
Click to collapse
Thank you. I've managed to unlock bootloader, but now I have new issue.
In TWRP phone turned off while installing new EU ROM (RMX2202_ROLLBACK_Android11_EUEX_0609) and now it's going to bootloader all the time. When I'm trying to boot to TWRP I have:
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.801s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.815s
What can I do now?

Had to reinstall stock ROM via paid service. Now I'm trying again with EU ROM. Can you recommend me good GDPR ROM to install?

Related

Moto e (indian version) flashing error

So, here is the problem i am facing with my moto E
I followed the tutorials from this site and had flashed my MOTO E to stock ROM 3-4 times due to different reasons, i was successfully able to do that using the STOCK ROM that i had for android kitkat 4.4.4. Last month i updated my moto E to android lollipop. After that it kept asking me to install a 12MB update which i tried installing quite some times but was not able to install. It showed some error while installing the same. So, i started ignoring that. A couple of days ago i once again tried to install that update and after installing the update when the phone turned on, it logged on into FASTBOOT MENU saying:
hab check failed for boot
failed to validate boot image
Fastboot reason: Fall-through from normal boot mode
So, i thought Flashing it once again might solve the issue. When i tried flashing it, on the command screen it gives ERROR for 4 files i.e. boot.img, system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2 saying::
<bootloader> invalid signed image
<bootloader> preflash validation failed
And on my phone screen it says "Invalid PIV signed image"
For all other instructions it says OKAY
Now it is again and again turning ON into this fastboot mode only...
Since i already had flashed my moto using the same custom rom , i think the files must be okay...
PLEASE HELP :'(
Why did you flashed 4.4.4 and then ota updated to 5.1 ? This process should've bricked your device in the first place.
Anyway 5.1 stock image files are available, did you tried flashing them? (fastboot mode)
-z3r0- said:
Why did you flashed 4.4.4 and then ota updated to 5.1 ? This process should've bricked your device in the first place.
Anyway 5.1 stock image files are available, did you tried flashing them? (fastboot mode)
Click to expand...
Click to collapse
sorry, i didn't knew that i shouldn't update my phone after installing the stock rom. No i haven't tried flashing my phone with android 5.1 stock file, i thought maybe flashing my phone with android 4.4.4 will downgrade my phone back to kitkat. Will try it now...will be helpful to me if you could get me a link for android 5.1 stock file as well, i tried finding the same, but it says for moto e2 which comes originally with lollipop but mine comes with android 4.4, its so confusing for me which stock file to download....
thanks for the help
Here : http://forum.xda-developers.com/showthread.php?t=2755857
"RetailDSDS" - Is for Indian version
-z3r0- said:
Here : http://forum.xda-developers.com/showthread.php?t=2755857
"RetailDSDS" - Is for Indian version
Click to expand...
Click to collapse
tried it, still giving the same error, preflash validation error :'(

Unable to install Lineage lineage-14.1-20170125-nightly

Hi, I am trying to install the lineage-14.1-20170125-nightly, but I get the following error:
This package supports bootloaders: MSM8226C00B322_Boot; This device has bootloader MSM8226C00B128_Boot. The updated process ended with Error 7. Error installing zip file '/sdcard/lineage-14.1-20170125-nightly-mt2-signed.zip'.
I am not sure if I have the correct bootloader.
c:\adb>fastboot oem get-bootinfo
.
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.016s]
finished. total time: 0.016s[/SIZE]
I have tried to follow the link below, but some of the direct links to the files are not working:
https://forum.xda-developers.com/as...iew-cyanogenmod-mate-2-mt2l03-t3181518/page52
Could anyone help me out with this thanks.
You have to install TWRP, once installed reboot into TWRP, Wipe then install Lineage OS, su(arm) addon, then open Gapps.
Here is a video on how to install TWRP: https://www.youtube.com/watch?v=sjA4F_TzzwQ
You can find the newest TWRP for the MT2 here (its near the bottom of the page, do not download the version of Lineage OS on that page ONLY TWRP): https://android.cmphys.com/lineageos-mt2/
Then download Open Gapps (click on ARM>7.1> then choose which variant, i use PICO, but other variants have more Google Apps): http://opengapps.org/
Download an official Nightly of Lineage: https://download.lineageos.org/mt2
Download "su (arm)" addon for Root access in Lineage, Flash this a long with Lineage: https://download.lineageos.org/extras
here is another useful video of SuperBass installing a different rom on the MT2 to kind of give you an idea on what to do: https://youtu.be/Tq27VfRYKYQ
Good luck!
Thank you for the quick reply.
NightCrayon said:
You have to install TWRP, once installed reboot into TWRP, Wipe then install Lineage OS, su(arm) addon, then open Gapps.
Here is a video on how to install TWRP: https://www.youtube.com/watch?v=sjA4F_TzzwQ
You can find the newest TWRP for the MT2 here (its near the bottom of the page, do not download the version of Lineage OS on that page ONLY TWRP): https://android.cmphys.com/lineageos-mt2/
Then download Open Gapps (click on ARM>7.1> then choose which variant, i use PICO, but other variants have more Google Apps): http://opengapps.org/
Download an official Nightly of Lineage: https://download.lineageos.org/mt2
Download "su (arm)" addon for Root access in Lineage, Flash this a long with Lineage: https://download.lineageos.org/extras
here is another useful video of SuperBass installing a different rom on the MT2 to kind of give you an idea on what to do: https://youtu.be/Tq27VfRYKYQ
Good luck!
Click to expand...
Click to collapse
Hi, I have followed all the above instructions, but i am still getting the same error. Since there is no OS installed, I have performed the following steps:
1 . Downloaded the twrp-3.0.M6-0-mt2.img and renamed it to TWRP.
2 . Rebooted the phone into bootloader mode and flashed the phone with the twrp-3.0.M6-0-mt2.img (twrp).
3. Rebooted the phone into recovery mode.
4. Wiped the phone to factory settings and also wiped the /system, data, cache, except internal storage.
5. Used the adb push command to transfer the rom, extra (su arm), and gapps to the external memory.
6. Upon flashing the rom I get the error below:
This package supports bootloaders: MSM8226C00B322_Boot; This device has bootloader MSM8226C00B128_Boot. The updated process ended with Error 7. Error installing zip file '/sdcard/lineage-14.1-20170125-nightly-mt2-signed.zip'.
Please let me know if I am missing anything. Thanks again
It is a wind Mobile phone that i am trying to flash it to linage 14.1. I don't have stock rom installed because I wiped /system accidentally.. As stated in my first post that I tried to check the bootloader version, but all I get is the following result below:
-----------------------------------------------------------------------------------
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
-----------------------------------------------------------------------------------
I don't know whether ' 001.001.000' means it is an old bootloader or latest. I would also like to mention that I was able to flash the phone to cm13.1 nightly, but the wifi was not working and security under settings was crashing.
I tried to update the bootloader 322 from the link below with B321_stock p19 recovery.zip under B321 folder:
https://drive.google.com/drive/fold...9VZ0ExZmhWS2VSUnNieUc4QTRRUVVZM2dLOHlRTnhNVDg
When I try to flash the phone with B321recovery.img it gives me an error FAILED (remote: size too large). See the result below:
c:\adb>fastboot flash recovery c:\adb\B321recovery.img
< waiting for device >
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.074s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.087s
Please any help appreciated.
techswy said:
It is a wind Mobile phone that i am trying to flash it to linage 14.1. I don't have stock rom installed because I wiped /system accidentally.. As stated in my first post that I tried to check the bootloader version, but all I get is the following result below:
-----------------------------------------------------------------------------------
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
-----------------------------------------------------------------------------------
I don't know whether ' 001.001.000' means it is an old bootloader or latest. I would also like to mention that I was able to flash the phone to cm13.1 nightly, but the wifi was not working and security under settings was crashing.
I tried to update the bootloader 322 from the link below with B321_stock p19 recovery.zip under B321 folder:
https://drive.google.com/drive/fold...9VZ0ExZmhWS2VSUnNieUc4QTRRUVVZM2dLOHlRTnhNVDg
When I try to flash the phone with B321recovery.img it gives me an error FAILED (remote: size too large). See the result below:
c:\adb>fastboot flash recovery c:\adb\B321recovery.img
< waiting for device >
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.074s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.087s
Please any help appreciated.
Click to expand...
Click to collapse
The wind Mobile variant of the MT2 has a little bit of a different process for updating the bootloader, follow this guide to install the last official B322 update, then you will have no problems with installing lineage as your bootloader will be up to date.
https://forum.xda-developers.com/ascend-mate2/general/guide-step-step-wind-mobile-canada-t3387490
Let me know if you have anymore issues. Good luck!
NightCrayon said:
The wind Mobile variant of the MT2 has a little bit of a different process for updating the bootloader, follow this guide to install the last official B322 update, then you will have no problems with installing lineage as your bootloader will be up to date.
https://forum.xda-developers.com/ascend-mate2/general/guide-step-step-wind-mobile-canada-t3387490
Let me know if you have anymore issues. Good luck!
Click to expand...
Click to collapse
Thank you so much for the link. I will definitely let you know if I run into more issues with the upgrade. Thanks again.
Yes, the newer custom ROMs require you to have flashed B322 (Huawei's final Lollipop ROM) first before flashing the custom ROMs. They have these warnings in the posts.
In the future, if you want to switch from one custom ROM to another, like from Lineage to CM, you won't need to flash B322 again as you would have already done this.
ScoobSTi said:
Yes, the newer custom ROMs require you to have flashed B322 (Huawei's final Lollipop ROM) first before flashing the custom ROMs. They have these warnings in the posts.
In the future, if you want to switch from one custom ROM to another, like from Lineage to CM, you won't need to flash B322 again as you would have already done this.
Click to expand...
Click to collapse
Thanks for the reply. I really appreciate the response. :good:
Thank you xda forum, NightCrayon and ScoobSTi for helping me fix my phone. Thanks again.
You must be from Wind Mobile from Canada
techswy said:
Hi, I am trying to install the lineage-14.1-20170125-nightly, but I get the following error:
This package supports bootloaders: MSM8226C00B322_Boot; This device has bootloader MSM8226C00B128_Boot. The updated process ended with Error 7. Error installing zip file '/sdcard/lineage-14.1-20170125-nightly-mt2-signed.zip'.
I am not sure if I have the correct bootloader.
c:\adb>fastboot oem get-bootinfo
.
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.016s]
finished. total time: 0.016s[/SIZE]
I have tried to follow the link below, but some of the direct links to the files are not working:
https://forum.xda-developers.com/as...iew-cyanogenmod-mate-2-mt2l03-t3181518/page52
Could anyone help me out with this thanks.
Click to expand...
Click to collapse
You must from Canada. You have to change your device from MSM8226C00B128 to MSM8226C00B322. Flow the link blow. This link will guide you to change to B322 and upgrade to Android 5.1.
https://forum.xda-developers.com/ascend-mate2/general/guide-step-step-wind-mobile-canada-t3387490
vivek76 said:
You must from Canada. You have to change your device from MSM8226C00B128 to MSM8226C00B322. Flow the link blow. This link will guide you to change to B322 and upgrade to Android 5.1.
https://forum.xda-developers.com/ascend-mate2/general/guide-step-step-wind-mobile-canada-t3387490
Click to expand...
Click to collapse
Hi, I'm having the same issue and I am using firmware B322 Lollipop 5.1. So I think something else is afoot. I'm going to try and update to Marshmallow cm13 first. But, I have to assemble cm13 myself, unless someone can get me a copy I would surely appreciate it.
sevenday4 said:
Hi, I'm having the same issue and I am using firmware B322 Lollipop 5.1. So I think something else is afoot. I'm going to try and update to Marshmallow cm13 first. But, I have to assemble cm13 myself, unless someone can get me a copy I would surely appreciate it.
Click to expand...
Click to collapse
Candy is so much better have you tried that yet?
https://www.androidfilehost.com/?w=files&flid=151179
I was finally able to install Lineage lineage-14.1 awhile back. I figured out where to get the Rom and modify it in order to flash it on my mtl02. But, it's been acting kinda kinky so for grins I'm going to try Candy that divhandyman suggested. ?
divhandyman said:
Candy is so much better have you tried that yet?
https://www.androidfilehost.com/?w=files&flid=151179
Click to expand...
Click to collapse
I have just flashed Candy ? about two weeks ago. Had some issues with substratum and magisk. I guess it was because you need a certain version of TWRP. Then a few days ago I with the LOD (loop of death). Lineage had the same issue

Is it hardbrick ?

Hi, After updated my Moto Z (XT1650-03) to oreo from OTA, I unlocked the bootloader in order to root phone. But I couldn't root the phone. And it did not boot. Then I flashed stock 7.1.1 (GRIFFIN_NPL26.118-20-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) and the phone turned on. The phone does not power up after I try to install OTA updates. No reaction. Is it hardbrick ?
tekin96 said:
Hi, After updated my Moto Z (XT1650-03) to oreo from OTA, I unlocked the bootloader in order to root phone. But I couldn't root the phone. And it did not boot. Then I flashed stock 7.1.1 (GRIFFIN_NPL26.118-20-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) and the phone turned on. The phone does not power up after I try to install OTA updates. No reaction. Is it hardbrick ?
Click to expand...
Click to collapse
hi dude, mmm i have a similar problem, so i think you have a hard bricked device. My moto z doesnt power up and doesnt charge it is dead
I had a similar problem after a failed downgrade from Oreo to Nougat. My phone was bricked over a month but it works now since the factory image of Oreo is out. I had earlier had a working blankflash but due to security limits I wasn't able to flash anything that would downgrade the system (so nothing really).
The blankflash file I found in the unbrick guide a while ago. Erfanoabli posted the Blank flash file but I'm not sure on witch page but it should be the latest version you can find.
The factory image I found in Android Oreo update -chanels- thread on page 37, and should work for every device except RETCN apparently. I unpacked the zip and flashed it in fastboot after I booted up to fastboot with the blank flash file.
Worked like a charm!
It still says RETEU when I go to settings.
Now I can stop using my backup phone!
I can't post any links unfortunately since I'm not a senior member.
PS. If you want to root Oreo you have to be careful! Read the guides. Otherwise you might get a bootloop.
JohanSjogren said:
I had a similar problem after a failed downgrade from Oreo to Nougat. My phone was bricked over a month but it works now since the factory image of Oreo is out. I had earlier had a working blankflash but due to security limits I wasn't able to flash anything that would downgrade the system (so nothing really).
The blankflash file I found in the unbrick guide a while ago. Erfanoabli posted the Blank flash file but I'm not sure on witch page but it should be the latest version you can find.
The factory image I found in Android Oreo update -chanels- thread on page 37, and should work for every device except RETCN apparently. I unpacked the zip and flashed it in fastboot after I booted up to fastboot with the blank flash file.
Worked like a charm!
It still says RETEU when I go to settings.
Now I can stop using my backup phone!
I can't post any links unfortunately since I'm not a senior member.
PS. If you want to root Oreo you have to be careful! Read the guides. Otherwise you might get a bootloop.
Click to expand...
Click to collapse
Hi I have the same problem, I had Nougat 7.1.1 update to version 8.0 and make a drowngrade to 7.1, then I received an update of the security patch, it was then when it was Hard Bricked (no power up no charge) , I thinkneed a blankFash for the version of Oreo. do you think the flash did you used from the message you mention would?.
Thanks in advance
JohanSjogren said:
I had a similar problem after a failed downgrade from Oreo to Nougat. My phone was bricked over a month but it works now since the factory image of Oreo is out. I had earlier had a working blankflash but due to security limits I wasn't able to flash anything that would downgrade the system (so nothing really).
The blankflash file I found in the unbrick guide a while ago. Erfanoabli posted the Blank flash file but I'm not sure on witch page but it should be the latest version you can find.
The factory image I found in Android Oreo update -chanels- thread on page 37, and should work for every device except RETCN apparently. I unpacked the zip and flashed it in fastboot after I booted up to fastboot with the blank flash file.
Worked like a charm!
It still says RETEU when I go to settings.
Now I can stop using my backup phone!
I can't post any links unfortunately since I'm not a senior member.
PS. If you want to root Oreo you have to be careful! Read the guides. Otherwise you might get a bootloop.
Click to expand...
Click to collapse
Erfanoabli's blankflash works for me too. Can you please help me about what Im going to do ? I dont want to do someting wrong.
Edit : Now My phone powers up on Stock Oreo!! Firstly I flashed gpt.zip. After I flashed GRIFFIN_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Thank you so much.
tekin96 said:
Erfanoabli's blankflash works for me too. Can you please help me about what Im going to do ? I dont want to do someting wrong.
Edit : Now My phone powers up on Stock Oreo!! Firstly I flashed gpt.zip. After I flashed GRIFFIN_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Thank you so much.
Click to expand...
Click to collapse
Hi ,
Im trying to flash back to stock oreo but using the same GRIFFIN_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml package i cannot flash the boot.img i keep receiving this message :
C:\Temp\Tools\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.107s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.834s]
finished. total time: 0.943s
any ideas ?
Scugy said:
Hi ,
Im trying to flash back to stock oreo but using the same GRIFFIN_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml package i cannot flash the boot.img i keep receiving this message :
C:\Temp\Tools\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.107s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.834s]
finished. total time: 0.943s
any ideas ?
Click to expand...
Click to collapse
Firstly you should flash gpt.zip which is in 15 page of [GUIDE] Unbrick hard bricked Moto Z topic. After that you can flash the stock oreo.

Question Error going back to miui.

Hello, i have this problem with my Redmi note 10, i was on a custom rom AOSP and i decided to revert back to miui.
I tried to flash official rom using mi flash tool but i get this error which you can see in the screenshots.
Sometimes the flash tool may take 10 minutes but still flashing nothing. My phone is now stuck on fastboot page and i can still accest miui recovery 5.0 but i don't know what is it used for. Any solution to this please?
.
[Solved] Fastboot flash super error - FAILED (remote: 'failed to check sparse crc')
Hi, I'm getting an error trying to install stock rom from xiaomirom.com via fastboot. D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea>fastboot flash super...
forum.xda-developers.com
devcon69 said:
[Solved] Fastboot flash super error - FAILED (remote: 'failed to check sparse crc')
Hi, I'm getting an error trying to install stock rom from xiaomirom.com via fastboot. D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea>fastboot flash super...
forum.xda-developers.com
Click to expand...
Click to collapse
what am i supposed to do please? should i flash a xiaomi.eu rom?
thanks anyway, i fixed it by installing a new firmware from another website.
AlexWilson said:
thanks anyway, i fixed it by installing a new firmware from another website.
Click to expand...
Click to collapse
What solution you find , tell me plis I have same problem
Juniorrn said:
What solution you find , tell me plis I have same problem
Click to expand...
Click to collapse
try a different miui version

FAILED (remote: please install correct signature)

Code:
PS E:\root\GREE> .\fastboot flash recovery twrp-recovery-v1.2.img
target reported max download size of 536870912 bytes
sending 'recovery' (48973 KB)...
OKAY [ 1.089s]
writing 'recovery'...
FAILED (remote: please install correct signature)
finished. total time: 1.114s
I get this error when trying to flash TWRP on my phone, IDK what the signature means here .. ?
The phone defends you from uploading the wrong file. Are you sure you are flashing the right file for your phone model? Did you compare the checksum after downloading the file with the checksum posted on the download page?
More info:
How to install TWRP recovery on Android smartphones
Installing TWRP on an Android device is the first step towards custom development.
www.xda-developers.com
ze7zez said:
The phone defends you from uploading the wrong file. Are you sure you are flashing the right file for your phone model? Did you compare the checksum after downloading the file with the checksum posted on the download page?
More info:
How to install TWRP recovery on Android smartphones
Installing TWRP on an Android device is the first step towards custom development.
www.xda-developers.com
Click to expand...
Click to collapse
Yes, I followed a Chinese forum that says they have flashed the same twrp img for this specific phone (GREE G0215D) but it's preventing me from flashing it on the phone is there any way around it?
Phone specs
Look first for a way to unlock the booloader based on the thread:
Install Google Play Services on Chinese Phone (Gree G0215D)
Hi there, I received a Gree G2015D Phone as a gift from a Chinese friend. (Here is a Russian Site showing the phone) It comes with a 6.0.1 based Rom but without google play services installed. There are a lot of guides how this can be done for...
forum.xda-developers.com
I can't advise anything else. Good luck.
ze7zez said:
Look first for a way to unlock the booloader based on the thread:
Install Google Play Services on Chinese Phone (Gree G0215D)
Hi there, I received a Gree G2015D Phone as a gift from a Chinese friend. (Here is a Russian Site showing the phone) It comes with a 6.0.1 based Rom but without google play services installed. There are a lot of guides how this can be done for...
forum.xda-developers.com
I can't advise anything else. Good luck.
Click to expand...
Click to collapse
Thank you for answering but I already unlocked the bootloader, do you think the error is from the twrp.img ?
Mark Wasfy said:
Thank you for answering but I already unlocked the bootloader, do you think the error is from the twrp.img ?
Click to expand...
Click to collapse
The way I understand it, the message comes from fastboot and is a response from the phone's bootloader to an attempt to upload data to the protected recovery partition.

Categories

Resources