Hello everyone I have been havinng some issues with my realme 8 RMX 3085. I was planning to install Lineage OS and custom recovery. I followed tutorials on xda. Fortunately i unlocked bootloader with official method - deeptest.apk, to do this firstly I flashed rom with thailand one. Everything seems to be succesfull, in settings bootloader is unlocked.
fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (131072 KB)...
OKAY [ 5.336s]
writing 'recovery'...
OKAY [ 0.451s]
finished. total time: 5.788s
However after that I am not able to enter recovery (even stock one). I kept flashing recovery image via fastboot. Everything seems to be all right until I try to enter it. Using command fastboot reboot recovery nothing happens. Another one adb reboot recovery tries to enter recovery several times with no success, then reboot to os.
I read couple of threads about that issue, tried using different computers, with different os - still the same. Tried using different cables and usb ports also nothing changed.
Does anyone have any idea what can couse the problem? Appreciate any advices.
Same here, trying few days but nobody help
Ok..did you installed magisk by flashing magisk patched boot.img ? If yes..then you need to restore/flash stock boot.img to enter recovery..this problem occurs on android 12 only..
https://telegra.ph/Flash-LineageOS-on-Realme-8-06-05
try follow this tutorial, worked for me
Related
Hello!
Having a pretty big problem, as I am trying to help my girlfriend get her phone all recovered and usable again for her. On our HTC Ones, we both use Android Revolution HD and were updating to the latest (4.4 version). With my phone, the installation of TWRP 2.6.3.3, then the rom went completely fine.
On her phone, it is going terribly. I made one mistake and forgot to copy the ROM over to the device before I wiped her system, so I don't have the new file to flash. I attempted to flash the old ROM, which was sitting on her device, but it is extremely slow to the point of we waited about an hour or two and it never installed. I have attempted to sideload, but the file is copying much slower than expected. Heck, everything involving the filesystem is running slow, even data wipes! I tried a full system erase, so now I am at a position where we have no flashable ROMS on the device.
I have tried both adb push and adb sideload to send the file, and both never successfully complete, even after waiting hours.
Where do I go from here? Any idea why flashing roms and file system is running so slow?
Change USB port/cable/computer and try push/sideload again
sent from my mobile device
SaHiLzZ said:
Change USB port/cable/computer and try push/sideload again
sent from my mobile device
Click to expand...
Click to collapse
I tried this already. I know this is not the cause as installing a zip of a new rom literally takes about 2 hours to write to the system.
Even a fastboot flash recovery takes about 30 seconds on her device, tested with multiple cables on two macbook pros. My HTC One flashed normally in less than a second...
When I flashed recovery:
MacBookownloads limitin$ fastboot flash recovery recovery.img
sending 'recovery' (9184 KB)...
OKAY [ 1.333s]
writing 'recovery'...
OKAY [ 0.696s]
finished. total time: 2.029s
When I flashed her phone with the same recovery file (TWRP 2.6.3.3):
MacBookownloads limitin$ fastboot flash recovery recovery.img
sending 'recovery' (9948 KB)...
OKAY [ 1.450s]
writing 'recovery'...
OKAY [ 35.708s]
finished. total time: 37.158s
Same phone. Some hboot version. Only thing I had to do to hers first (I had done mine previously) was use revone to s-off her device, which was successful after a few attempts.
So I wanted to flash TRWP recovery via fastboot but everytime I try it it fails saying:
Code:
D:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
target reported max download size of 1514139648 bytes
sending 'recovery' (12534 KB)...
OKAY [ 1.593s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.740s
My bootloader is unlocked and S-off
(Maybe its worth mentioning that my phone is stuck in the bootscreen)
Anyone who knows what the problem could be?
zabdelicious said:
So I wanted to flash TRWP recovery via fastboot but everytime I try it it fails saying:
Code:
D:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
target reported max download size of 1514139648 bytes
sending 'recovery' (12534 KB)...
OKAY [ 1.593s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.740s
My bootloader is unlocked and S-off
(Maybe its worth mentioning that my phone is stuck in the bootscreen)
Anyone who knows what the problem could be?
Click to expand...
Click to collapse
Ok I managed to flash TWRP, but theres another problem... I wanted to flash a stock htc m7 rom via an otg cable and flash drive. The rom is in the root of the stick but when I select the stick in twrp its empty
zabdelicious said:
Ok I managed to flash TWRP, but theres another problem... I wanted to flash a stock htc m7 rom via an otg cable and flash drive. The rom is in the root of the stick but when I select the stick in twrp its empty
Click to expand...
Click to collapse
What format is your usb stick? NTFS won't work with otg, try formatting the usb as fat32 copy the rom back on and try again.
What version of TWRP are you using? Newer versions use MTP in recovery so you can just 'drag and drop' the rom to your storage from recovery mode
Sent from my SM-T230 using Tapatalk
Danny201281 said:
What format is your usb stick? NTFS won't work with otg, try formatting the usb as fat32 copy the rom back on and try again.
What version of TWRP are you using? Newer versions use MTP in recovery so you can just 'drag and drop' the rom to your storage from recovery mode
Click to expand...
Click to collapse
Thanks now it worked, however there occurred another problem. When I flash the rom via otg, the phone reboots and is again stuck in the htc logo screen. I've waited couple of minutes but nothing happened
zabdelicious said:
Thanks now it worked, however there occurred another problem. When I flash the rom via otg, the phone reboots and is again stuck in the htc logo screen. I've waited couple of minutes but nothing happened
Click to expand...
Click to collapse
Which version of twrp are you using? And which rom are you flashing? Also normally I would recommend copying the rom from the OTG to the internal storage then install it from there. :good:
It's also worth noting a successful clean install can take 15 to 20 min to pass the htc boot logo, on first boot.
Sent from my SM-T230 using Tapatalk
Hello. So, I got my Moto G5s Plus around the last week of October or beginning of November. It is a great device, but I learned about the camera flaws by Motorola and unlocked the bootloader to fix it by following this XDA thread here for camera fixing and the Chromatix mod. I learned that I could edit build.prop without flashing the TWRP recovery but using it temporarily following the guide here. build.prop edit would enable cam2api for third party cam apps. The Chromatix mod threads/posts were for the G5 Plus, which I didn't realize at the time and didn't backup original Chromatix files. However, That went successfully and I could still use my phone with better camera quality. Note that prior to doing this fix and before unlocking the bootloader (I believe) I had updated my device from Nougat to Oreo. My bootloader is indeed unlocked.
Now, when the 1 October OTA Update came I was hesitent because I had came across some rooting/custom rom/custom recovery/mod articles while learning about unlocking the bootloader. Yet and before reading more to get educated on this, I applied the update to my phone. I was hoping it wouldn't brick it or that it would fail if it didn't work. It failed (because of the modification on the stock ROM) at the last bit of the update and rebooted my phone. My phone worked and it let me know nothing was changed by the failed update. However, my phone since then has shown as if it is up-to-date in system updates.
So, basically I have been trying to flash TWRP for my Moto G5s Plus after that was done. I want to see about backing up my stock ROM (or the most important parts) possibly getting a good custom ROM installed (which I believe they have their own official Android security updates from Google?). However flashing TWRP hasn't worked. I get the following in PowerShell (cmd):
PS C:\Android SDK\platform-tools> fastboot flash recovery twrp.img
Sending 'recovery' (10236 KB) OKAY [ 0.407s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.172s]
Finished. Total time: 0.594s
Note that I renamed twrp-3.1.1-sanders.img to twrp.img as it was a suggestion I followed at the time. This I heard is normal, but when I go to Recovery Mode on my phone I see this:
Start Up Failed:
Repair message stuff
AP Fastboot Flash Mode (Secure)
Fastboot Reason: UTAG *bootmode* configured as fastboot
~~~
Error: failed to load kernel!
~~~
I also tried to find the latest stock ROM to flash because I believe I read I may need to do that. I found SANDERS_RETAIL_8.1.0_OPSS28.65-36-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and tried to use "Apply update from ADB" from the stock Recovery (when it was working normally after powering off and not with kernel errors because of this). It failed.
I couldn't find the right answer(s). Thank you to anyone that can help me or others who have done the same!!
EDIT (11/19/2018):
So, last night I tried wiping my data in stock recovery and then I tried to do this again. It still didn't work. I also tried to apply the same stock zip as well as boot_magisk.img from this thread here https://forum.xda-developers.com/moto-g5s-plus/development/stock-kernel-prerooted-8-1-0-t3863301.
PS C:\Android SDK\platform-tools> fastboot flash boot boot_magisk.img
Sending 'boot' (10702 KB) OKAY [ 0.391s]
Writing 'boot' (bootloader) Image not signed or corrupt
OKAY [ 0.141s]
Finished. Total time: 0.563s
It all still fails. However, now when I boot up my phone it goes straight to the bootloader instead of loading the OS right away. I can select START to start the phone normally from there.
I got all this resolved through XDA's Telegram group (& specific group for G5s Plus/sanders)! I have TWRP (Treble) and custom rom working after getting an official stock rom from them flashed using fastboot commands!
I don't know if I should or a mod can close/erase this thread now?
Try typing fastboot oem fb_mode_clear while in bootloader
Coala990 said:
Try typing fastboot oem fb_mode_clear while in bootloader
Click to expand...
Click to collapse
Thanks for the suggestion/tip. I will probably try that if I reflash twrp treble (or another version of twrp for Sanders) again. This has been resolved.
I'm so to ask such a newb question, but I'm all out of ideas.
I unlocked the bootloader on my Mi 9 - I have the Chinese version.
I enabled developer options and turned on USB Debugging.
I downloaded TWRP.
I verified that I could push commands to my phone by rebooting it - adb reboot bootloader
That worked just fine. The phone booted to bootloader.
Then I tried to flash TWRP.
C:\Users\***\Documents\TEMP>fastboot flash recovery twrp-3.2.3-1-cepheus-mauronofrio.img
target reported max download size of 536870912 bytes
sending 'recovery' (56928 KB)...
OKAY [ 1.275s]
writing 'recovery'...
OKAY [ 0.305s]
finished. total time: 1.582s
C:\Users\***\Documents\TEMP>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\Brett\Documents\TEMP>
From what I can tell, the flash worked. I see no errors.
Following the instructions I see over at the Cyanogenmod forums, I held the Volume Up button.
The phone immediately went to bootloader.
I tried Volume Up and the Power button.
The phone immediately went to bootloader.
I saw somewhere that for phones that are Oreo and later, to use "recovery_ramdisk" but that partition does not exist.
It's almost like there is no recovery that I can boot up. I'm not sure what I am doing wrong.
Has anyone run into this before?
Thanks!
funmunke said:
I'm so to ask such a newb question, but I'm all out of ideas.
I unlocked the bootloader on my Mi 9 - I have the Chinese version.
I enabled developer options and turned on USB Debugging.
I downloaded TWRP.
I verified that I could push commands to my phone by rebooting it - adb reboot bootloader
That worked just fine. The phone booted to bootloader.
Then I tried to flash TWRP.
C:\Users\***\Documents\TEMP>fastboot flash recovery twrp-3.2.3-1-cepheus-mauronofrio.img
target reported max download size of 536870912 bytes
sending 'recovery' (56928 KB)...
OKAY [ 1.275s]
writing 'recovery'...
OKAY [ 0.305s]
finished. total time: 1.582s
C:\Users\***\Documents\TEMP>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\Brett\Documents\TEMP>
From what I can tell, the flash worked. I see no errors.
Following the instructions I see over at the Cyanogenmod forums, I held the Volume Up button.
The phone immediately went to bootloader.
I tried Volume Up and the Power button.
The phone immediately went to bootloader.
I saw somewhere that for phones that are Oreo and later, to use "recovery_ramdisk" but that partition does not exist.
It's almost like there is no recovery that I can boot up. I'm not sure what I am doing wrong.
Has anyone run into this before?
Thanks!
Click to expand...
Click to collapse
Try this dm-verity disabler
https://zackptg5.com/android.php#disverfe
What I did is like this
Flash rom
Flash dm-verity disabler
Flash magisk
Done
BTW, I don't quite understand your problem
Your phone stuck in bootloader or TWRP?
For TWRP you can try that dm-verity disabler
Thanks, this saved my life. I had problems with
"FAILED (remote: Token Verify Failed, Reboot the device)"
After i flashed the last rom i used(Pixel Experince) with this dm-verity disable it workes now !!
funmunke said:
I'm so to ask such a newb question, but I'm all out of ideas.
I unlocked the bootloader on my Mi 9 - I have the Chinese version.
I enabled developer options and turned on USB Debugging.
I downloaded TWRP.
I verified that I could push commands to my phone by rebooting it - adb reboot bootloader
That worked just fine. The phone booted to bootloader.
Then I tried to flash TWRP.
C:\Users\***\Documents\TEMP>fastboot flash recovery twrp-3.2.3-1-cepheus-mauronofrio.img
target reported max download size of 536870912 bytes
sending 'recovery' (56928 KB)...
OKAY [ 1.275s]
writing 'recovery'...
OKAY [ 0.305s]
finished. total time: 1.582s
C:\Users\***\Documents\TEMP>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\Brett\Documents\TEMP>
From what I can tell, the flash worked. I see no errors.
Following the instructions I see over at the Cyanogenmod forums, I held the Volume Up button.
The phone immediately went to bootloader.
I tried Volume Up and the Power button.
The phone immediately went to bootloader.
I saw somewhere that for phones that are Oreo and later, to use "recovery_ramdisk" but that partition does not exist.
It's almost like there is no recovery that I can boot up. I'm not sure what I am doing wrong.
Has anyone run into this before?
Thanks!
Click to expand...
Click to collapse
many users run into this problem, including me.
just boot to bootloader, flashing latest twrp
don't restart your phone using command, just press vol. up + power
you'll directly booting into twrp in few seconds
tawa2525 said:
Try this dm-verity disabler
https://zackptg5.com/android.php#disverfe
What I did is like this
Flash rom
Flash dm-verity disabler
Flash magisk
Done
BTW, I don't quite understand your problem
Your phone stuck in bootloader or TWRP?
For TWRP you can try that dm-verity disabler
Click to expand...
Click to collapse
I can't get TWRP to come up. I flash the image and then try to boot to recovery, but there is no recovery. When you try to get fastboot.
ain_gt said:
many users run into this problem, including me.
just boot to bootloader, flashing latest twrp
don't restart your phone using command, just press vol. up + power
you'll directly booting into twrp in few seconds
Click to expand...
Click to collapse
I tried that and got fastboot instead of TWRP
funmunke said:
I tried that and got fastboot instead of TWRP
Click to expand...
Click to collapse
So...I figured it out. You are going to laugh at me.
That version of TWRP was garbage. I switched to another version and now I'm up and running.
Thanks to everyone who responded!
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
I need help :'(
I had that.
Phone was completely dead, needed a new board.
chrissyyyw said:
I had that.
Phone was completely dead, needed a new board.
Click to expand...
Click to collapse
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?
benkiller47 said:
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?
Click to expand...
Click to collapse
I booted into fastboot, flashed the individual firmware files and it kept failing on the vendor.
I had a black screen with a red flashing LED on reboot. I claimed on my insurance and they replaced the board on the phone.
I checked on here and online for a resolution and it generally points to a hard brick.
benkiller47 said:
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
Click to expand...
Click to collapse
You must use OTG! Probably Flashify borked a partition,but i don't think it borked vendor.
However, you should still be able to flash a FullOTA with TWRP + NoCheck combo.
If you can't manage that, hit me on Telegram,i'm @Pretoriano80 in there!
You can flash EMUI based FW using an OTA method. It should work. But it will lock your bootloader and you will have to unlock it again.
benkiller47 said:
Hi
Click to expand...
Click to collapse
Are you flashing the same or later firmware??