Hi guys!
Wo, i've got a question about Realme 7 bootloader, since i dont really know where else i could ask.
I unlocked my phone using THIS guide.
Everything went smoothly, until the end. After the phone rebooted, i tried going into fastboot mode (bootloader). Well... I encountered a problem:
For a few seconds, there was a string of numbers, and at the bottom was this message:
"the serial is not match.
fastboot_unlock_verify fail"
Sorry for the bad quality
{
"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"
}
And well, i wanted to ask if anyone had simillar issue, and do you maybe know how to fix it?
I think you would be able to install a custom recovery and ROM within the recovery menu cause the Fastboot mode is only enabled thru the DeepTest which I don't think it worked (it also didn't in my situation)
DaCrab said:
I think you would be able to install a custom recovery and ROM within the recovery menu cause the Fastboot mode is only enabled thru the DeepTest which I don't think it worked (it also didn't in my situation)
Click to expand...
Click to collapse
Well, actually fastboot worked after i flashed stock ROM, but i couldnt boot at all to the bootloader. But i still wasnt able to install TWRP through realme recovery, idk how to even do this.
I red in a forum that someone had the same problem but managed to install a custom recovery thru the recovery menu cause the fastboot mode
I had also managed to do the same but I didn't have any custom recovery afterwards idk why but when I tried it just kep flashing "Recovery..." and not redirecting me anywhere
DaCrab said:
I red in a forum that someone had the same problem but managed to install a custom recovery thru the recovery menu cause the fastboot mode
I had also managed to do the same but I didn't have any custom recovery afterwards idk why but when I tried it just kep flashing "Recovery..." and not redirecting me anywhere
Click to expand...
Click to collapse
Hmm this is a weird problem. First and last time buying realme phone for anything root-related haha. I also had a problem with magisk, since it just said "download failed" after i tried flashing it in recovery. I did download the .apk file and rename it for zip file, zo it should be good to go, but idk.
Hello Realme 7 user,
Don't worry I had this problem too, I had a hard time unlocking the bootloader and after that I was disappointed fastboot wasn't working when I entered the RUI recovery, for most phones fastboot is enabled after you unlock the bootloader and the key combination for Realme 7 isn't actually POWER BUTTON + VOLUME DOWN, this key combination will bring you in the normal RUI recovery.
I found a method which is working but I don't know if it really depends on the firmware (I was using RUI1 A10 when I found this) but you actually boot into the OS, then go to developer options, enable USB debugging and fire up an ADB Shell and then type adb reboot fastboot.
Don't be scared, it will reboot into the RUI recovery but fastboot it's actually enabled now. You can verify if fastboot is enabled by typing fastboot devices. See if it works now.
Related
*deleted*
*deleted*
*deleted*
Hi, i can't help you for now, but i have your same smartphone and i want to make a cwm recovery.
I've been rooted succesfully the phone and i made a cwm for this device, does anyone know how put the you25 in fastbootmode?
*deleted*
your help will be apprecciated,
the phone if of my girlfriend and now, after tryng to flash a cwm recovery built by the online builder,the you25 is still in bootloop.
Fortunately, I made a backup of the stock recovery and now i have to reflash it.
I need to know how put the phone in fastboot mode or eventually how reflash all the entire system, (before my girlfriend knows what i did:crying.
If you are interested, i made a cwm porting that works for 50%, you can backup and restore all entire system; then i tried the online builder to make it 100% working but with no success.
*deleted*
*deleted*
No, i can't access adb, i need to put it in fastbootmode by pressing at startup a sequence of buttons. (Es, power+vol down or whatever else for this devise).
Now i see the android logo only plugyng the power cable, it still appears for about 3-4 seconds, then the backlight of the three buttom buttons lights on and then the device reboots.
Initially, I flashed the recovery by adb, after rooted the mobile and mounted the filesystem in r/W mode with:
Code:
dd if=/sdcard/recovery.img of=/dev/blocks/mtdblocks10
.
You can find the right number by typing in adb shell:
Code:
cat /proc/partitions/
I have experience with other device, generally you can flash with adb, fastboot and by download mode, if the device boots you can always fix it, but you need the right tools.
*deleted*
mgbrain said:
what happens when you boot the device by normal start, does it also go into the 3-4 seconds bootloop or does it get stuck on the android logo?
i had my device stuck there already too but i was still able to access adb.
Click to expand...
Click to collapse
The device starts only if i plug the power cable, after 5-6 second the android logo shows up and then after 4 seconds the device reboots.
Adb doesn't work for me, but if you have adb working i think i can help you.
What is the last think you made to the device before beeing stock on the boot?
*deleted*
Thank you, but that doesn't work for me.
What about jtag? i have experience with decoders but nothing about smartphones.
Reading about how restore nexian a850, i founded that is possible to reflash the you25 with the sprocoom tool and the same driver of the nexian a850. Unfortunately I do not have the firmware for the you 25. Has anyone it, please?
I think that it is possible to flash the device using the img files that i created before and a prebootloader.
I have also to edit a file with a list of all partitions with their address in hex format.
Unfortunately i do not know these values, and i cannot see them from my device because it doesn't work. can anyone help me, please?
here is a list of all partitions:
{
"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"
}
I'm currently on CM 13.0-20160809-NIGHTLY-onyx and I've tried to flash three different Roms on my phone (Two different versions of cm14 and OOS3) with TWRP. But every time I get the error message attached in the screenshot.
Now, I've seen a few people online having similar problems, but it was mostly for cm12 and the suggested fixes are not really helpful for my situation.
I've somehow lost my stock backup so I'm kinda lost right 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"
}
In general Error 7 usually means you're using the wrong version of TWRP. I'm still using Blu_Sparks version for the new bootloader.
quoakkaflocka said:
I'm currently on CM 13.0-20160809-NIGHTLY-onyx and I've tried to flash three different Roms on my phone (Two different versions of cm14 and OOS3) with TWRP. But every time I get the error message attached in the screenshot.
Now, I've seen a few people online having similar problems, but it was mostly for cm12 and the suggested fixes are not really helpful for my situation.
I've somehow lost my stock backup so I'm kinda lost right here.
Click to expand...
Click to collapse
You need to upgrade your bootloader and TWRP.you are using very old CM and now everything is changed so upgrade your boot loader and recovery.
I already use TWRP 3.0.2-0 which is the newest version according to TWRP Manager.
How do I upgrade my bootloader?
Edit: So I found this way to do it :Link
The thing is: it says the bootloader must be unlocked, but if I type "fastboot devices" I get nothing back. "adb devices works. I'm pretty sure that my bootloader is unlocked since I have a custom rom and my device is rooted but I'm not sure if I have activated the CM recovery option in the developer settings ever since.
I really don't wanna brick my phone so I'm not sure if I should blindly follow the steps in the link above.
quoakkaflocka said:
I already use TWRP 3.0.2-0 which is the newest version according to TWRP Manager.
How do I upgrade my bootloader?
Edit: So I found this way to do it :Link
The thing is: it says the bootloader must be unlocked, but if I type "fastboot devices" I get nothing back. "adb devices works. I'm pretty sure that my bootloader is unlocked since I have a custom rom and my device is rooted but I'm not sure if I have activated the CM recovery option in the developer settings ever since.
I really don't wanna brick my phone so I'm not sure if I should blindly follow the steps in the link above.
Click to expand...
Click to collapse
"fastboot devices" doesn't work unless you are in the bootloader
I tried to upgrade from 7.4.16 to 7.5.1 by creating a flashable zip from huawei update extractor, and the zip file created by it include modem.img to flash to /dev/block/mmcblk0p30. so when i reboot it, the phone will stuck in Powered by ANdroid splash screen. trying to boot to recovery mode won't work. but by pressing vol+ vol- and power key, i can enter recovery mode, the stock recovery will try to flash sdcard/dload/update.app, but will fail at 5%. the twrp recovery is working but flashing normal zip including system, boot, cust won't help.
So one day I was searching how to flash modem.img and found out dc-phoenix tool can do that for honor 8. so i gave a try.
{
"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"
}
the tool is not free, i have to pay eur 15 to get a account to unbrick it. since huawei customer service costs about eur 8 in my area, i think its worthy.
To ensure, i try method 2 of it. this needs to download a factory image for my phone, click Enter Support area a web page will open, find firmware of my deivce, whick is
PLK-AL10_CM001026_Factory_firmware_general_Android_5.0_EMUI_3.1_testpoint.dgtk
my phone is already in fastboot mode, just connect it to pc, click update waiting...
after a long waiting finally its over, no error.
i use fastboot reboot to boot it and it just boots fine. so the phone is unbricked, but system is not useful, model became unkown. the factory version is emui 2.0, i can not upgrade to newer version.
so i need to try method 1 again. this time i downloaded emui 4.0 b388 from club.huawei.com, load it.
at first i used a wrong version for another phone model, it will always fail, so its important to make sure the rom is full stock one for the exact phone model. if third part adb/fastboot software exists, close them first, lick wandoujia, hisuite, qq... then click update to start.
when its ready, my phone can boot up fine with emui 4.0, but sim card is not working, so i had to continue the step 2. reboot to recovery with usb plugged in. this step was a lot slower then step 1 but just wait patiently.
At home this step always fail at writing file 21 of 22:System instantly, showing out of memory which is not normal since my pc
has 16g memory, and hard disk still has 8g left. But on my work pc, its fine, a little strange.
if this step failed, i think the best way is contact support or try in another pc. last night when it failed i try to flash via official method, shows cust update failed the reboot. i guess the sim not working is related to that.
when this step finished, the phone will reboot automatically.
Hi, I don't think that flashing that would help, can you acces the fastboot mode ? (vol down and power)
Cordially,
Blendman974 said:
Hi, I don't think that flashing that would help, can you acces the fastboot mode ? (vol down and power)
Cordially,
Click to expand...
Click to collapse
Thanks for the reply, i can access the fastboot mode, but can only flash cust, system, boot, recovery which i tested with several version of firmwares.
i unbricked the phone with dc-phoenix tool now, again, thanks for helping:silly:
I unlocked my bootloader and was using Havoc Os for a quite bit time and i wanted to switch to Stock OS(Realme UI) , so i flashed Stock OS from official site and flashed correctly and was using. Yesterday i flashed magisk through TWRP and i got locked my bootloader and now i am able to do anything with my phone just the message "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it" Is there anyway to fix this issue
{
"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"
}
. I tried Volume up button + power key and Volume down button + power button and both Volume up + down button and power key it keeps on poping the message "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
Please help me Developers.
How did you get locked my bootloader?
donkeyman1234 said:
How did you get locked my bootloader?
Click to expand...
Click to collapse
i dont know i justed flashed magisk.zip file and rebooted my phone and it locked . I dont know how
I think this post is quite similar to you, however can still boot into twrp till lock bootloader.
https://forum.xda-developers.com/realme-xt/help/bricked-realme-xt-help-neended-t4073807
donkeyman1234 said:
I think this post is quite similar to you, however can still boot into twrp till lock bootloader.
https://forum.xda-developers.com/realme-xt/help/bricked-realme-xt-help-neended-t4073807
Click to expand...
Click to collapse
no bro i can't boot into any mode thats my problem is there any tool to flash rom via pc?
Well, there do have some posts about flash rom, but I haven't used it, so you must
do it on your own risk. You can search it on google for more.
https://www.getdroidtips.com/stock-rom-realme-xt/
https://www.gsmmafia.com/realme-xt-rmx1921-flash-file/
I have already told you if you have locked bootloader only service center can fix your device
SarathEXP said:
I have already told you if you have locked bootloader only service center can fix your device
Click to expand...
Click to collapse
Due to lockdown the Service center are closed :crying::crying:
We’re you able to find any solution, I am also stuck and not able to boot in edl mode. With both volume up and down it boots in edl mode for sometime and then restart
rohitharkhani said:
We’re you able to find any solution, I am also stuck and not able to boot in edl mode. With both volume up and down it boots in edl mode for sometime and then restart
Click to expand...
Click to collapse
https://forum.xda-developers.com/re...realme-xt-stock-rom-ofp-t4018243/post82332155
any update here though?
Appreciate anyone who can help! I was tooling around trying to unlock my AT&T locked SD1 but was basically unable to get it working. So I decided to undo everything with a factory reset and relock the bootloader...and that's when I bricked my device.
I am unable to go past the bootloader screen and unable to either Start the device or enter Recovery Mode.
Not sure how else to proceed.
So, is the bootloader currently locked?
Does fastboot flashing unlock work?
Renate said:
So, is the bootloader currently locked?
Does fastboot flashing unlock work?
Click to expand...
Click to collapse
Unfortunately, no. Adb is no longer recognising the device and I'm stuck in boot select screen unable to even Start or enter Recovery Mode.
Bootloader is currently locked.
Not that it does a lot of good, but you can see fastboot?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what I see.
I think you are out of luck until the firehose programer for the DUO out. I got the same device like this. Maybe boot.img is broken for the device, or recovery partition got messed up. Basically the device have to restore from the ground up.
Sadly MSFT does not provide a restore solution other than the recovery image which the device have to enter the recovery mode at least.
JimmyRespawn said:
I think you are out of luck until the firehose programer for the DUO out. I got the same device like this. Maybe boot.img is broken for the device, or recovery partition got messed up. Basically the device have to restore from the ground up.
Sadly MSFT does not provide a restore solution other than the recovery image which the device have to enter the recovery mode at least.
Click to expand...
Click to collapse
I was worried you'd say something like that. Down in the dumps.
May be this can help you?
https://www.reddit.com/r/surfaceduo/comments/wn5joi
Sharkam said:
May be this can help you?
https://www.reddit.com/r/surfaceduo/comments/wn5joi
Click to expand...
Click to collapse
What in the name of all things holy?! Man, I'm gonna have to look deep into this and figure it out. Problem is, I am not nearly as smart as that guy which is itself gonna be a huge challenge. That said, I do have all the patched imgs on my desktop...so perhaps there is a way back. IF I can figure out the process as laid out here.
Thanks for this pal at least it helps.
im here with you i need bootimg from 2022.823.41 ota went threw now stuck.. im on the duo 2
This is the duo 1 forum.
There is a duo 2 forum, but it is less active.
did u tryed
`fastboot reboot recovery`
yes .. it just falls back to bl .. I need the boot.img from 2022.823.41 update . I tried to capture the link but it flashed before I told it.
this is the duo2 btw
Me too I have the same issue. Did you found how to fix it ?