(Realme 6) After flashing my phone with the original ROM, google pay doesn't work - Realme 6 Questions & Answers

So I tried installing a custom ROM on my Realme 6 a while ago and it didn't work out so I had to flash my phone with the stock ROM, after doing so, after every restart I get a boot message:
Orange State: Your device has been unlocked and can’t be trusted…Your device will boot in 5 seconds
The phone still boots alright but I cannot use google pay or specific services as it says that the phone cant be trusted.
Does anyone know of this and how to fix it? quite a frustration not being able to use my phone for paying anymore.
edit: i read that relocking the phone fixes it but i also read that you may hardbrick your phone. kinda lost.

soler37 said:
So I tried installing a custom ROM on my Realme 6 a while ago and it didn't work out so I had to flash my phone with the stock ROM, after doing so, after every restart I get a boot message:
Orange State: Your device has been unlocked and can’t be trusted…Your device will boot in 5 seconds
The phone still boots alright but I cannot use google pay or specific services as it says that the phone cant be trusted.
Does anyone know of this and how to fix it? quite a frustration not being able to use my phone for paying anymore.
edit: i read that relocking the phone fixes it but i also read that you may hardbrick your phone. kinda lost.
Click to expand...
Click to collapse
You unlocked the bootloader, you need to re-lock the bootloader, that is what the "device can't be trusted" message means.
Find a guide on the internet or a thread here that discusses unlocking/locking the bootloader on your specific model number, if other people with your exact model have re-locked their bootloader without bricking their device, follow the same instructions/steps exactly the way they did and you shouldn't have to worry about bricking the device if you carefully follow instructions to the letter.
If you already searched and found the solution, why did you come here to ask? It isn't like their is an alternative solution that can be found here. Lock your bootloader, that's it.

I found guides but wanted to make sure, anyway, I typed reboot bootloader command, and my phone restarts and is stuck with a message
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

soler37 said:
I found guides but wanted to make sure, anyway, I typed reboot bootloader command, and my phone restarts and is stuck with a message
Click to expand...
Click to collapse
Same happened with me brother...but in my case my twrp recovery got removed and now am stuck with this msg as in your post..and now i am little bit uneasy as i can get stuck on bootloop..what did you do after this?..did you flashed it again? Did it work?

Inevitable007 said:
Same happened with me brother...but in my case my twrp recovery got removed and now am stuck with this msg as in your post..and now i am little bit uneasy as i can get stuck on bootloop..what did you do after this?..did you flashed it again? Did it work?
Click to expand...
Click to collapse
Press and hold power + vol up and down, should turn on.
Anyway, I fixed my bootloader by flashing my phone with an older update.
I used this guide:

soler37 said:
Press and hold power + vol up and down, should turn on.
Anyway, I fixed my bootloader by flashing my phone with an older update.
I used this guide:
Click to expand...
Click to collapse
ya i know that process but i meant to ask that flashing twrp again caused any problem? or does the device even goes to stock recovery?

Inevitable007 said:
ya i know that process but i meant to ask that flashing twrp again caused any problem? or does the device even goes to stock recovery?
Click to expand...
Click to collapse
I didn't flash using twrp, I used SPFLASH tool and then after the process finished, my phone back to first update, I was then able to relock the bootloader using the normal commands.

soler37 said:
I didn't flash using twrp, I used SPFLASH tool and then after the process finished, my phone back to first update, I was then able to relock the bootloader using the normal commands.
Click to expand...
Click to collapse
ok thanks

Related

Root, How do adb fastboot commands work? need help

Hello, I am student at my university studying Computer Science. I work in tech support at my school. This is the first time I have modified the android os. The community on xda has been really helpful and knowledgeable. I have created an account to see if anyone else has done the same thing I have. Anyway read below for my post.
I am trying to change the recovery on my phone to twrp. Let me start out by saying I rooted my phone before on build number 130 (KIW-L24,Android 5.1,EMUI 3.1,C567B130,United States, Channel-Others). I used the instructions here and it worked http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190.
I then decided to update through the huawei updater to build number 151 (KIW-L24, Android 5.1, EMUI 3.1, C567B151, United States, Channel-Others). It eventually got to a black EMUI menu with installing 0%. So I powered it off even though it warned against it. So my phone was bricked so I followed instructions at http://forum.xda-developers.com/honor-5x/help/bricked-honor-5x-t3328308 and my phone worked again.
Okay so now I want to root my phone so I follow the instructions for rooting. Problem is that I can not replace the EMUI recovery with twrp recovery. I am guessing that it may be because 151 is a security update.
I use these commands on adb with the twrp_kiwi.img in my adb folder(named .android by default)
adb reboot bootloader
fastboot flash recovery twrp_kiwi.img
fastboot reboot
adb reboot recovery
So I wanted to see if I could put the old firmware back so I followed the instructions for bricked device. But the fastboot commands don't seem to do anything with the .img files.
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
Yea so I am lost as to why fastboot commands arent working as it says finished and any advice would be appreciated.
Also is it possible to format the phone similar to a pc and use adb to flash the firmware back on.
I want to eventually backup my phone and put cyanogenmod on it.
... I am guessing that it may be because 151 is a security update
Click to expand...
Click to collapse
If your bootloader is unlocked, you should be able to flash what you want.
Have you tried reinstalling the Android device drivers on your PC?
JT-on said:
If your bootloader is unlocked, you should be able to flash what you want.
Have you tried reinstalling the Android device drivers on your PC?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Arobase40 said:
Is this really for a private use unless you are trying to ask us to do your university exercises for you ? LOL
And as you felt need to mention "I am student at my university studying Computer Science. I work in tech support at my school.", you should know first University mission is to teach you to search and exercise by yourself, to do things step by step and to guess by yourself what was wrong. ^^
Just one tip and advice : read up your own post carefully and you should find out what you've done wrong...
Click to expand...
Click to collapse
That was just background information unrelated to my post. I am currently trying to see if I can put the old firmware back to see if it fixes the problem.
honor5x_student said:
That was just background information unrelated to my post. I am currently trying to see if I can put the old firmware back to see if it fixes the problem.
Click to expand...
Click to collapse
TWRP works just fine on B151
plug in usb / Shut down the phone
boot to the bootloader (power + vol down)
open command prompt on PC
fastboot flash recovery twrp_kiwi.img
hold volume up + volume down + power till you see TWRP (about 14 seconds)
In TWRP choose reboot / recovery
Say yes to Root
recovery will reload / flash your rom
If you want to return to Stock use this >> https://www.androidfilehost.com/?fid=24459283995315154
instructions are in the zip

Start Error in Pixel Experince, by Boot.img flashed by Fastboot (phone almost brick).

Hello friends, I hope you are well. I am writing to everyone to see if anyone can help me with this big problem.
Yesterday install the Rom Pixel Experience, all good, all the steps to perfection and others, had microSD at that time so flash the boot.img by Fastboot. It seems to install the Boot.img in the Recovery TWRP partition, or something like that. Because I do not have the Recovery either, when I try to go to the recovery, the window "Bootloader Unlocked" appears, but it does not take me anywhere, only to the boot of the rom, it is something very strange and the truth scares me. I clarify: I can not access the Fastboot, nor the download mode, nor the recovery, because it does not.
There will be another way: ????
PLEASE IF SOMEONE CAN HELP ME, FIND ANOTHER METHOD TO ENTER THE FASTBOOT OR DOWNLOAD MODE, THE SOLUTION THAT WORKS WILL PAY ME WELL TO THE PROPONGA, PLEASE, I DO NOT WANT TO LOSE MY MOBILE, I BUY IT WITH A LOT OF EFFORT.
Last night I dawned on the boot logo, until it was completely downloaded and at this moment it continues to do so ... By GOD!
When trying to enter the Fastboot or download mode, it takes me here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Image extracted from: https://www.tomshw.it
Then he starts loading the rom and stays there all the time .:
Image extracted from: https://www.tomshw.it
I can not access Fastboot, nor download mode, nor recovery, because it has disappeared. There will be another way to enter the Fastboot or download mode, because the phone actually woke up until I wake up today and was even charged. PLEASE.
Hey, sorry for your sad state. Following process worked for me when I got stuck yesterday like that.
1. Connect your phone to PC ( make sure adb/fast boot is setup)
2. Hard reboot your phone with power plus volume down button.
3. As soon as your phone turns off, press volume down only and keep it pressed till you enter fastboot.
4. After this phone should be recognised in PC and you should be able to boot in TWRP using fastboot.
ZestyManu said:
Hey, sorry for your sad state. Following process worked for me when I got stuck yesterday like that.
1. Connect your phone to PC ( make sure adb/fast boot is setup)
2. Hard reboot your phone with power plus volume down button.
3. As soon as your phone turns off, press volume down only and keep it pressed till you enter fastboot.
4. After this phone should be recognised in PC and you should be able to boot in TWRP using fastboot.
Click to expand...
Click to collapse
Hope this works for you @Yeriorlando. @gimpy1 had a similar issue when installing Havoc ROM. Part of the problem seems to be when installing the custom kernel?
gimpy1 said:
It was operator error (generally is) on my part, I'm sure. The only thing I did different that I can remember is installing the 9.0 boot image in twrp differently. I installed it in the recovery option first (intentionally, should not have), instead of ticking only the boot choice. I did not untick the recovery option (should have never ticked it in the first place, but I was trying to correct a problem on the ROM, and misread a post).
Click to expand...
Click to collapse
He was able to reinstall TWRP using fastboot.
gimpy1 said:
Thx, Chaz. I pulled out my printed instructions from your post, and once I was able to get my device recognized (that did take a couple of tries), reinstalling twrp was pretty easy.
I'm back in business thanks to you.:good:
Click to expand...
Click to collapse
IF you still can't after the suggestion at top, maybe @SGCMarkus or @runningnak3d have some tips?
Unless you have an H932, then if you get the error that: "Your device software can't be checked for corruption" then you have fastboot. It is literally impossible to have that message on a WTF rooted phone and NOT have working fastboot.
So, as @ZestyManu said -- make *sure* your phone is powered off. If you have to let, the battery die. Then hold vol down + plug in the USB cable (no need to touch the power button) and you will enter fastboot.
-- Brian
Thank you all. I have solved the problem in a super crazy way, to pure ADB, not fastboot .... Pure ****ing adb ... Hehehehe. Thanks to @ChazzMatt

UNOFFICIAL LANCELOT TWRP Released

UNOFFICIAL TWRP Released but no one dare to test it,
Anyone can told me, can I go ahead to flash twrp ????
Source Link : https://unofficialtwrp.com/xiaomi-redmi-9-root-twrp-3-4-1/
https://unofficialtwrp.com/xiaomi-redmi-9-root-twrp-3-4-1/
Update :
Sample twrp Pictures of Lancelot
<img src="https://i.ibb.co/nbLQbgT/IMG-20200905-211641-263.jpg" alt="IMG-20200905-211641-263" border="0">
It is very risky to test it.....I already brick my device twise....I have no dear to flash it.no need to flash it now...I can root my phone without it...once any custom ROM relase then I definitely try it.
There is no TWRP recovery. This link is fake. This is a tutorial how to to apply TWRP recovery. But no one can build a TWRP recovery now for redmi 9 because the source code is not released yet. I think you understand
Someone already installed twrp here is the pics
<img src="https://i.ibb.co/nbLQbgT/IMG-20200905-211641-263.jpg" alt="IMG-20200905-211641-263" border="0">
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Proof of TWRP installed in Redmi 9 Lancelot
Telegram @redmi_9indonesia
I flashed this recovery and YES it works but you need to be EXTREMELY careful coz it is VERY buggy! Booted into it a few times and after my device became unresponsive and then BRICKED with no access to the bootloader! I ended up formatting it with SP Flash Tool and in the process re-locked the bootloader. Now Xiaomi wants me to wait for another 336 hours to unlock
nielsync said:
I flashed this recovery and YES it works but you need to be EXTREMELY careful coz it is VERY buggy! Booted into it a few times and after my device became unresponsive and then BRICKED with no access to the bootloader! I ended up formatting it with SP Flash Tool and in the process re-locked the bootloader. Now Xiaomi wants me to wait for another 336 hours to unlock
Click to expand...
Click to collapse
We do not need to install TWRP recovery because of there is no custom ROM and the source code is not release yet so please please do not do this dumb thing. I brick my phone to time and learn that the device is not for play because it is a MediaTek processed mobile phone
Chances of getting into a boot loop are 99% if you flash this unofficial TWRP. I was lucky I knew how to restore my device without taking it to a service center!
nielsync said:
Chances of getting into a boot loop are 99% if you flash this unofficial TWRP. I was lucky I knew how to restore my device without taking it to a service center!
Click to expand...
Click to collapse
Yes I know you follow my instruction and that's why you do not need to go to to customer centre..,...
Yeah I happened to see your instructions AFTER I restored. The 'magic' is the secure boot DA loader file that supports the Redmi 9 MTK chip and which is contained in Mi Flash Pro. I actually used the standalone SP Flash Tool to restore the phone having managed to obtain the mentioned loader file from Program Files after installing Mi Flash Pro. I have always had a number of Tecno and Infinix devices that are usually MTKs so I knew the risk and how to get out of it beforehand!!!
Check attachment who has issue,
https://ibb.co/hVVxF0x
mark332 said:
Check attachment who has issue,
https://ibb.co/hVVxF0x
Click to expand...
Click to collapse
Yes you did it...is it safe to use....
mark332 said:
Check attachment who has issue,
https://ibb.co/hVVxF0x
Click to expand...
Click to collapse
That's very misleading. Showing a screenshot doesn't mean the recovery is functional because its not! It does not even respond to touch input and remains like that until you press the power key to turn off the screen.
nielsync said:
That's very misleading. Showing a screenshot doesn't mean the recovery is functional because its not! It does not even respond to touch input and remains like that until you press the power key to turn off the screen.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=83503955&postcount=1
Read this....

Can't update rooted N10

I have been trying to update my phone but everytime I try the OTA it says installation failed. I ignored it for a few months now bc I didn't want to lose root after updating. How can I install the OTA? I am on MetroPCS (BE88CF)
I tried disabling AdAway thought it may be blocking the servers but that didn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pulled this from the OnePlus website
"Ok, looks like the download has failed/corrupted. Open the File Manager app > go to settings in the FM app and enable "Show Hidden Files" > then go to the device storage and look for a folder called ".OTA" - delete it and its contents. Then reboot your phone and try again."
Did you ever figure this out? I have the same problem. Not even unrooting fixes it. There is no .OTA folder on my phone either.
doodalydoo said:
Did you ever figure this out? I have the same problem. Not even unrooting fixes it. There is no .OTA folder on my phone either.
Click to expand...
Click to collapse
Flash stock boot.img for your model and firmware. Probably gonna need the original recovery image too if you've got anything besides stock.
Relock bootloader using fastboot.
As long as there's nothing that can be checked back as invalid, you should be able to update your phone proper.
ninjasinabag said:
Flash stock boot.img for your model and firmware. Probably gonna need the original recovery image too if you've got anything besides stock.
Relock bootloader using fastboot.
As long as there's nothing that can be checked back as invalid, you should be able to update your phone proper.
Click to expand...
Click to collapse
I tried reflashing stock recovery and boot images, but it didn't work. Relocking the bootloader shouldn't be necessary, but if it is I'll just go without updating. I don't feel like having to wipe out my phone to unlock the bootloader again every time there is an update.
doodalydoo said:
I tried reflashing stock recovery and boot images, but it didn't work. Relocking the bootloader shouldn't be necessary, but if it is I'll just go without updating. I don't feel like having to wipe out my phone to unlock the bootloader again every time there is an update.
Click to expand...
Click to collapse
Sadly it's a boatload of effort to get the update. Either you go back to 100% stock, or live with it.
I said screw it and just moved everything to my memory card before using the msm reset app
ninjasinabag said:
Sadly it's a boatload of effort to get the update. Either you go back to 100% stock, or live with it.
I said screw it and just moved everything to my memory card before using the msm reset app
Click to expand...
Click to collapse
I managed to get the last update installed by reinstalling 11.0.2 through the Oxygen Updater, then 11.0.3 installed fine. I was going to try to repeat this method with 11.0.3 to get to 11.0.4, but Oxygen Updater no longer allows me to download 11.0.3. I tried to sideload it and do a local update, but the phone won't find it. I can't even install it through fastboot commands because the OTA is incremental and the payload dumper won't work on it.
I was able to update by doing what you said and relocking the bootloader after reflashing stock and boot images. Relocking bricked the phone so I had to use the unbrick tool. Definitely a pain to have to do this every time, Then I ran into problems restoring my TWRP backup that I had to figure out lol. I'll probably just update every two or three updates from now on. Plus all this reflashing opens up more opportunities for RCS features to stop working on Google Messages because they are so finicky. Then my texts act up for 3-10 days until RCS starts working again. Luckily they reconnected right away this time.
Thanks for the help.

help with whatever i have done

disclaimer - sorry i really have no idea what i am doing and my goal is to just go back to my normal phone
my phone is poco f1 and now i can only access fastboot and this "powered by android" screen. fastboot into twrp doesnt work because of "boot command is not allowed in lock state" error
hello all so i tried rooting my phone and then realized that its going really badly (i have a more details about it down) so i decided to flash stock rom using techno treatment's tutorial on it but along the way i have faced a couple of problems - when trying to install drivers, program crashes, and others below
first time i flashed i got an error (timeout error in logs) , so i tried to flash again but this time i left it open for some time (at around 500 seconds i pressed flash again, in logs it shows that flashing already started) and when i came back it was at 12000 seconds still flashing so i closed miflash and am flashing once again but with a shorter folder path (desktop\xiaomi\firmware).
after this i deleted 2 lines in flash_all.bat because i kept getting stuck on echo mismatching image and device. after this everytime i try to flash i get this error - error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State')
and also error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State') in the other log file
and after this i tried to go into fastboot but noticed that the fastboot logo is different, it was a bunny with a hat repairing android robot but now it is android robot repairing itself
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(this is what it looks now)
what i did before flashing stock - sorry my memory isnt the best this is all in a span of around 5 hours and my phone is pocophone f1. so at first i followed munchys tutorial on how to root, i succesfully enabled bootloader then in twrp i flashed recovery with some errors like failed to mount /system and 3 others like this but i ignored and continued then i installed magisk and after that in the video he goes into his phone no problem but i had "no os" and i think i just clicked around like backing up, restoring and wiping. then i thought i need a rom because its an os right? so i installed lineage and that was the last time when i could put files into my phone through usb. then i flashed the zip and after that rebooted and got "cant load android system, your data may be corrupt" so i pressed format something like that and did it a few times (i think this is when i couldnt put my files) until eventually saw that its no use so i went back to twrp and again clicked around until eventually wiping everything now i have no os and i cant transfer anything through usb.
Hi @medioqre
Seems like you are in locked bootloader state. You can not flash any ROM with locked bootloader unless you are enter EDL mode. See youtube tutorial to access edl mode for Beryllium
khusika said:
Hi @medioqre
Seems like you are in locked bootloader state. You can not flash any ROM with locked bootloader unless you are enter EDL mode. See youtube tutorial to access edl mode for Beryllium
Click to expand...
Click to collapse
Hi, to confirm - entering edl mode requires me to open up my phone right? how would i do that and how would i close it up after?
Thank you!
medioqre said:
Hi, to confirm - entering edl mode requires me to open up my phone right? how would i do that and how would i close it up after?
Thank you!
Click to expand...
Click to collapse
That's right, but i recommend go to the service center if you aren't able to do it.
khusika said:
That's right, but i recommend go to the service center if you aren't able to do it.
Click to expand...
Click to collapse
Hi again, its been 10 days.
so i have not went to a service center yet, because my city is too small for that. But i have a question. i didnt do anything else with my phone but today i decided i could do something and i booted it and i found out i can access fastboot mode and recovery mode, and in here i can see -
main menu, mi-recovery 3.0
and this one option
"connect with miassistant" which just gives me a picture of a phone if its plugged or unplugged with usb and under theres is a link to this website pcsuite.mi.com which doesnt work.
does this change my situation?
medioqre said:
Hi again, its been 10 days.
so i have not went to a service center yet, because my city is too small for that. But i have a question. i didnt do anything else with my phone but today i decided i could do something and i booted it and i found out i can access fastboot mode and recovery mode, and in here i can see -
main menu, mi-recovery 3.0
and this one option
"connect with miassistant" which just gives me a picture of a phone if its plugged or unplugged with usb and under theres is a link to this website pcsuite.mi.com which doesnt work.
does this change my situation?
Click to expand...
Click to collapse
If you are still in locked bootloader, you can't write firmware through fastboot or recovery
Why don't you try unlocking the bootloader officially?

Categories

Resources