Related
Stock kernels with the "forceencrypt" flag changed to "encryptable".
These are "IMG" files that need to be flashed with fastboot.
(Oct) N6F27M-noencrypt-boot.img - https://mega.nz/#!e4AmQJTa!-b9VEDCUHMa2YedScgHpSpStmKfhVWQMFWQf93L0OCU
(Oct) NGI77B-noencrypt-boot.img - https://mega.nz/#!XsBR0QBb!nkNQibCAT-IMpGH3pPVKLmHsGzE90JQfBcDzkWWwHEM
(Sept) NGI55D-noencrypt-boot.img - https://mega.nz/#!6sYSUbTb!dT-pBFhY4iJuHcqGWnRZiFvnUHLxVlNxrDDfgl0L_9w
(Aug) N6F27I-noencrypt-boot.img - https://mega.nz/#!atxQSZYK!y4H4uFt8pNW0szhUyWrp_QinytKIE3WhszAQMNJ4rO0
(Aug) N8I11B-noencrypt-boot.img - https://mega.nz/#!voxiWQqY!DtV5VWhRRLH3cvpxL37QJDFGMUjZU9uubBP8NuADG0k
Hi, and which one is to use? Are these carrier specific versions?
day242 said:
Hi, and which one is to use? Are these carrier specific versions?
Click to expand...
Click to collapse
Sounds like the N8I11B build has some Verizon specific code. After reviewing, it appears they devs used the same kernel in both builds, so it should not matter which is flashed.
Lose data?
Can these be flashed without losing data?
My Nexus 6 is currently not encrypted and I'd like to keep it that way, but don't want to have to reinstall all my apps and files. Again.
Thanks.
TheTomahawk said:
Can these be flashed without losing data?
My Nexus 6 is currently not encrypted and I'd like to keep it that way, but don't want to have to reinstall all my apps and files. Again.
Thanks.
Click to expand...
Click to collapse
You can update your phone and stay un-encrypted by flashing the latest "system.img", "cache.img", and the appropriate "noencrypt-boot.img" from the OP. (This is how I update each release and maintain the exisiting data)
Re: lose data
jbaumert said:
You can update your phone and stay un-encrypted by flashing the latest "system.img", "cache.img", and the appropriate "noencrypt-boot.img" from the OP. (This is how I update each release any maintain the exisiting data)
Click to expand...
Click to collapse
Cool. Em, could you provide instructions, please?
Tnx
TheTomahawk said:
Cool. Em, could you provide instructions, please?
Tnx
Click to expand...
Click to collapse
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
jbaumert said:
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
Much obliged.
im assuming one of these brings back ota? probably N6F27I
guessing one is official ota from 7.0 to 7.1.1
hello. can anyone please explain to me how do i get rid of encryption if i'm on lineage os? i am trying for hours now but every time my phone boots it is still encrypted. what i'm doing is i flash this modified boot.img through fastboot, then format userdata through fastboot, then go into recovery and wipe everything possible and then i flash latest los build from usb-otg. reboot and it's still encrypted :|
dudikaz said:
hello. can anyone please explain to me how do i get rid of encryption if i'm on lineage os? i am trying for hours now but every time my phone boots it is still encrypted. what i'm doing is i flash this modified boot.img through fastboot, then format userdata through fastboot, then go into recovery and wipe everything possible and then i flash latest los build from usb-otg. reboot and it's still encrypted :|
Click to expand...
Click to collapse
After flashing LOS and before booting the first time is when you need to flash a non-encrypted kernel. Flashing the boot.img before isn't doing any good as it's overwritten by the LOS install....
jbaumert said:
After flashing LOS and before booting the first time is when you need to flash a non-encrypted kernel. Flashing the boot.img before isn't doing any good as it's overwritten by the LOS install....
Click to expand...
Click to collapse
if i flash it after los it gets stuck on google logo and doesn't boot at all :/
---------- Post added at 01:08 AM ---------- Previous post was at 12:36 AM ----------
ok so now i've went back to stock N8I11B which is force encrypted. could you tell me exactly what steps should i take to make it not encrypted please? also what about the franco kernel does it get rid of encryption as well maybe?
If your flashing stock via fastboot, then you just need to replace the boot.img with the non-encrypted. That said, you will need to erase "userdata" also and start fresh. (Once user data is encrypted, it can't be "un-done" it's a start from scratch)
As for LOS, I've never used it with the stock kernel, but it sounds like its not compatible. Franco should work fine and is also not force-encrypt.
jbaumert said:
If your flashing stock via fastboot, then you just need to replace the boot.img with the non-encrypted. That said, you will need to erase "userdata" also and start fresh. (Once user data is encrypted, it can't be "un-done" it's a start from scratch)
As for LOS, I've never used it with the stock kernel, but it sounds like its not compatible. Franco should work fine and is also not force-encrypt.
Click to expand...
Click to collapse
it's really confusing as this is what it says in the official los thread here on xda - "Current lineage 14.1 shamu nightlies are based on the N8I11B August 2017 update from google. So you should be using the radio and bootloader img from that update. " also how do i erase this userdata properly? "fastboot format userdata"? i think last time i did it my device didn't boot at all afterwards. going to try it again now.
Added September 2017 "no encrypt" boot.img to OP
Added October 2017 "no encrypt" boot.img to OP
thumbs up !!!
i was looking all over for the latest img. really grateful for your work. thanks a lot
Thank you very much
jbaumert said:
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
Would we want to change the name of noencrypt-boot.img to boot.img before flashing or leave as is? Also can we make a backup in TWRP of our userdata and just restore after flashing as long as it's before booting the phone?
Jeffro64 said:
Would we want to change the name of noencrypt-boot.img to boot.img before flashing or leave as is? Also, can we make a backup in TWRP of our userdata and just restore after flashing as long as it's before booting the phone?
Click to expand...
Click to collapse
You can leave the name of the file (unless you just want to type in a short command with fastboot). As for the backup of "userdata", if you are updating the phone from one stock version to another and following the instructions you quoted, there is no need to backup. Coming from another ROM you would want to wipe and then yes, a backup is a good idea (needed).
i know there are other threads on this topic. But after going through them I cant find the fix.
I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works.
I used lmsa to download the stock rom. installed magisk and ran the boot.img to get the patched boot. Then flashed the patched boot and when i rebooted the device...no touchscreen.
I tried to reflash the original boot.img but that didnt help.
I tried to use LMSA to rescue. but when i connect the phone it says "unable to match firmware. Some key information cannot be read from device."
The original adb fastboot was old. So I did update to the r30 version and tried flashing everything again. but it still boots up and no touchscreen.
Im obviously at a loss here. so any help would be appreciated. Just to even get it back to stock would be fine.
Or do I try to install twrp and throw a custom rom on? would that work. Again, at a loss...
TIA
UPDATE: ive gotten everything sorted. no more bootloop. touchscreen working. connecting to lmsa. and rooted. Thank you for all the responses.
I think what happened is that when i started all this i was not using the latest adb. That seemed to not be an issue for unlocking bootloader, but a major issue for rooting. When i tried to root,i got the no touchscreen. So I followed directions and went to manually flash the stock firmware. I didnt know how to do this and couldnt find instructions for the g power. but did find instructions for the g8 power and assumed it would be the same...its almost the same, but not, so i got the bootloop.
These are the instructions:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
I added fastboot flash super super.img_sparsechunk.15, because the g8 power only has 14 sparsechunks and thats why i kept getting the bootloop. very stupid mistake that was driving me nuts! Once i added that 15th line the phone booted up and touchscreen worked again.
Then i installed magisk manager. Took the boot.img file from my stock rom and put it on my phone. back in magisk i clicked on install a patch file, chose the boot.img and created a magisk_patched.img which i put back into the adb folder i previously used to flash the firmware.
Then went back to fastboot and flashed the magisk_patched.img and the phone is now working and rooted...THANK GOD
cnoevl21 said:
i know there are other threads on this topic. But after going through them I cant find the fix.
I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works.
I used lmsa to download the stock rom. installed magisk and ran the boot.img to get the patched boot. Then flashed the patched boot and when i rebooted the device...no touchscreen.
I tried to reflash the original boot.img but that didnt help.
I tried to use LMSA to rescue. but when i connect the phone it says "unable to match firmware. Some key information cannot be read from device."
The original adb fastboot was old. So I did update to the r30 version and tried flashing everything again. but it still boots up and no touchscreen.
Im obviously at a loss here. so any help would be appreciated. Just to even get it back to stock would be fine.
Or do I try to install twrp and throw a custom rom on? would that work. Again, at a loss...
TIA
Click to expand...
Click to collapse
Flash stock ROM manually, it will fix the problem
riyan65 said:
Flash stock ROM manually, it will fix the problem
Click to expand...
Click to collapse
The US stock ROM does not have a 'flash all' option. So i have no idea how to flash it. ugh
cnoevl21 said:
The US stock ROM does not have a 'flash all' option. So i have no idea how to flash it. ugh
Click to expand...
Click to collapse
I just ran into the same problem and asked you about it in the other thread. Right after, I tried the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC and got my touchscreen back.
https ://mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/
I found out more of what's going on and posted in the other thread:
I just did the same exact thing. LMSA gave me SOFIA_RETAIL_QPMS30.80_51_8. Lost touchscreen with the patched boot. Used the stock 30.80_51_8 boot and didn't fix it. Also tried the older QPMS30.80-51-3, no dice.
Oh and LMSA can't rescue... key information cannot be read from device.
I'd appreciate any help. Thanks.
UPDATE - found the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC got the screen working again.
UPDATE 2 - patching -5 still left me no touchscreen. Went back to stock -5 and didn't work. Tried -8 and works again... I'm confused.
UPDATE 3 - when phone booted up, it notified me -8 was just installed... Patched -8 boot again and everything appears to be working fine. Moral of story - LMSA downloads the correct firmware if you give the phone enough time to finish auto-updating before rooting. SMH
haanjamin said:
I found out more of what's going on and posted in the other thread:
I just did the same exact thing. LMSA gave me SOFIA_RETAIL_QPMS30.80_51_8. Lost touchscreen with the patched boot. Used the stock 30.80_51_8 boot and didn't fix it. Also tried the older QPMS30.80-51-3, no dice.
Oh and LMSA can't rescue... key information cannot be read from device.
I'd appreciate any help. Thanks.
UPDATE - found the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC got the screen working again.
UPDATE 2 - patching -5 still left me no touchscreen. Went back to stock -5 and didn't work. Tried -8 and works again... I'm confused.
UPDATE 3 - when phone booted up, it notified me -8 was just installed... Patched -8 boot again and everything appears to be working fine. Moral of story - LMSA downloads the correct firmware if you give the phone enough time to finish auto-updating before rooting. SMH
Click to expand...
Click to collapse
good info to know. but now ive gone i screwed my phone up even worse. cuz now im stuck in boot loop. i was trying 105-5, but ill try 51-5, then -8. maybe one of them is the right stupid firmware for my phone
Do not panic.
Follow this guide to flash correct ROM, and patch boot from the ROM to get root
https://forum.xda-developers.com/moto-g-power/how-to/moto-g-power-flashing-guide-t4159301
mingkee said:
Do not panic.
Follow this guide to flash correct ROM, and patch boot from the ROM to get root
https://forum.xda-developers.com/moto-g-power/how-to/moto-g-power-flashing-guide-t4159301
Click to expand...
Click to collapse
ive tried this. i either dont have (and dont know) which is the correct rom. or some other issue. i can get into fastboot mode, no problem. but when i type fastboot reboot fastboot i get that long list of commands, as if im typing in a bad command. and it does not go into fastbootd. i can, however, get into fastbootd through recovery. but every time i try to flash something there, it fails (no file or directory).
And i cant use LMSA cuz when i try to connect, it says the phone has incorrect firmware.
Hello,
I've been looking through this forum for quite a while, but I have yet to stumble upon a guide that can fix me up for taking the next step after the bootloader unlocking process. Yet, there's been lots of custom roms made for rmx2001. So here I'm with my unlocked rmx2001 or realme 6, wondering if I am missing out on something crucial for the next step because this is my first time doing something like this on a mediatek based phone. Kindly help me out pweese.. thank you;
Update:
I've dwelled deep into the forest, fought clones of sundar pichai, then finally.. successfully flashed my phone with custom recovery.
From what I've had read around this forum and other places, before flashing any custom recovery, the vbmeta.img must be flashed with a patched one, which as usual, there are rules one must follow to modify this certain android component.
This is the first for me, as per Android 8 (or Android 7 with its super confusing arb system took in place), any changes inside the recovery, system, etc are being handled by this vbmeta module.
It seems that vbmeta.img changes for every android or system update and to patch this vbmeta.img, the android version must be the same as what the patch corresponds to... (correct me if I'm wrong; this is my understanding based solely from what I have read, please take this with a big chunk of salt).
I currently have the b.57 update installed on my device, and I only found b.55 here on the next forum's page... the point is I have to wait for the latest patch of vbmeta b.57. Am I understanding this correctly, or am I just talking in elven language to myself? Anyway thank you for reading.
zero help, good for nothing advices. Search on other forums ,you Will get at least real help
cristianwcw said:
zero help, good for nothing advices. Search on other forums ,you Will get at least real help
Click to expand...
Click to collapse
lmao
ignoll said:
From what I've had read around this forum and other places, before flashing any custom recovery, the vbmeta.img must be flashed with a patched one, which as usual, there are rules one must follow to modify this certain android component.
This is the first for me, as per Android 8 (or Android 7 with its super confusing arb system took in place), any changes inside the recovery, system, etc are being handled by this vbmeta module.
It seems that vbmeta.img changes for every android or system update and to patch this vbmeta.img, the android version must be the same as what the patch corresponds to... (correct me if I'm wrong; this is my understanding based solely from what I have read, please take this with a big chunk of salt).
I currently have the b.57 update installed on my device, and I only found b.55 here on the next forum's page... the point is I have to wait for the latest patch of vbmeta b.57. Am I understanding this correctly, or am I just talking in elven language to myself? Anyway thank you for reading.
Click to expand...
Click to collapse
Hi fellow weeb I'm curious of how did you manage to flash custom recovery?
Lyco. said:
Hi fellow weeb I'm curious of how did you manage to flash custom recovery?
Click to expand...
Click to collapse
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
Do you a vbmeta.img for the latest patches b.59 or any guide to extract vbmeta, Just like you said the vbmeta corresponds with the patch.
Lyco. said:
Do you a vbmeta.img for the latest patches b.59 or any guide to extract vbmeta, Just like you said the vbmeta corresponds with the patch.
Click to expand...
Click to collapse
We can just use the vbmeta.img from stock ROM .ozip
Thanks
HemanthJabalpuri said:
We can just use the vbmeta.img from stock ROM .ozip
Thanks
Click to expand...
Click to collapse
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right? Or do you have a stock vbmeta?
Lyco. said:
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right?
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Is this the stock vbmeta? Or do anyone have any?
Lyco. said:
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right? Or do you have a stock vbmeta?
Click to expand...
Click to collapse
No, we don't need to modify anything to it.
--disable-verity and --disable-verification options to fastboot will patch it and flash automatically for you.
Also you can use vbmeta.img from any version of stock .ozip.
I am a Realme C12 user.
Thanks
HemanthJabalpuri said:
No, we don't need to modify anything to it.
--disable-verity and --disable-verification options to fastboot will patch it and flash automatically for you.
Also you can use vbmeta.img from any version of stock .ozip.
I am a Realme C12 user.
Thanks
Click to expand...
Click to collapse
Ok so what would I do if pbrp didn't showed up? And goes to bootloop, Do i just need to flash ofp and use realme flash tool?
I'm a new at flashing firmware so sorry about that
Lyco. said:
Ok so what would I do if pbrp didn't showed up? And goes to bootloop, Do i just need to flash ofp and use realme flash tool?
I'm a new at flashing firmware so sorry about that
Click to expand...
Click to collapse
Then flash stock recovery.
HemanthJabalpuri said:
Then flash stock recovery.
Click to expand...
Click to collapse
So after i flash the stock recovery should I flash the ozip there? And thanks for all the information.
Yes, Im stuck. Im on realme 5i and I flashed PixelExperience+ with TWRP, clean flash, made sure to wipe data and clear cache before and after flashing. I rebooted and boom, stuck on fastboot/bootloader. I can't go back to recovery mode or to system, it just takes me back to fastboot/bootloader. I backed up my files btw.
Supposed fixes that did not work:
1: Fastboot erase boot && fastboot erase dtbo && fastboot erase recovery && fastboot erase vbmeta && fastboot erase system && fastboot erase userdata and fastboot flash recovery TWRP.img && fastboot flash dtbo dtbo.img && fastboot flash vbmeta vbmeta.img && fastboot reboot-bootloader.
- it brings me back to fastboot when I try to go to recovery mode.
2: Push volume down/up and power button.
- it brings me back to fastboot when I try to go to recovery mode. (2)
3: flash stock recovery (I can't go to recovery so I cant flash stock ROM too)
- it brings me back to fastboot when I try to go to recovery mode. (3)
What else do I do? Am I missing something from the fixes I've tried above?? I am in need of urgent help.
Update: I've tried realme flash tool, for stock ROM and it says cannot find central directory.
I've tried putting the ofp to AppData/Roaming/flashtool/temp as said from another thread. I've also tried running in administrator but none work. I've ran out of luck today, please help.
Phone: Realme 5i
Story: I had my phone get a custom recovery, TWRP. Got it rooted. Before I rooted it I rolledback to android 9, ColorOS, bw. Then decided why not use a custom ROM? So I did. PixelExperiencePlusEdition ANDROID 12. I flashed it with TWRP, factory reset and cleared cache, in other words, clean flash. I'm hopeless cause once I rebooted, I got sent to fastboot then when I tried to go to recovery mode, it sends me back to fastboot! What do I do? I need help. please.
Update: So maybe I am doing the 1st method wrong. I got all the img files wrong, cause I need them from my stock firmware right? So I tried programs to extract those img from their new.dat.br files right? I did and the extractors keep giving me something is missing, line this and that is incorrect or something like that. I'm really hopeless. Can someone give me the img files of RMX2030EX_11_OTA_0210_all_1hZhuZlgVC1t? system.img, boot.img, vendor.img, vbmeta.img, dtbo.img? What else am I missing to manually flash it?
I am facing the same issue as well, I had downloaded the RMX2030EX_11_C.75_210917_1b9832bb file and extracted using https://github.com/bkerler/oppo_decrypt but the first method still didn't work. was is the wrong file? or did the decryptor didn't work properly idk.
koarc lkas said:
Update: So maybe I am doing the 1st method wrong. I got all the img files wrong, cause I need them from my stock firmware right? So I tried programs to extract those img from their new.dat.br files right? I did and the extractors keep giving me something is missing, line this and that is incorrect or something like that. I'm really hopeless. Can someone give me the img files of RMX2030EX_11_OTA_0210_all_1hZhuZlgVC1t? system.img, boot.img, vendor.img, vbmeta.img, dtbo.img? What else am I missing to manually flash it?
Click to expand...
Click to collapse
I can't find a file on realme software page with this name where did you get the file? plus does your variant has Qualcomm or Mediatek CPU? I saw a video where it stated that this phone has two variants one with Qualcomm and other with Mediatek(Helio) CPU.
Edit: Do an MD5 check maybe your file got corrupt..
I managed to fix, you will need download these files from telegram. one of them should work for me the ColorOS file worked. Follow the instruction given in the readme file and that should do. I am installing DotOS now it showing the splash animation from last 5 minutes, if it works i'll update the comment or will provide further instructions to fix.
FastbootFix-Realme-5-5i-5s~RUI.zip
FastbootFix-Realme-5i~Color OS.zip
Edit: the reason it was taking so long to bootup and was stuck on splash animation is that I forgot to format (type yes).
yasir.r said:
I can't find a file on realme software page with this name where did you get the file? plus does your variant has Qualcomm or Mediatek CPU? I saw a video where it stated that this phone has two variants one with Qualcomm and other with Mediatek(Helio) CPU.
Edit: Do an MD5 check maybe your file got corrupt..
Click to expand...
Click to collapse
I got it from this:
This is what I used to rollback to android 9 cause another video said I had to do this first before rooting. It worked though then custom ROM happened and now phone's bricked. Hasn't been used ever since.
I'll do MD5 if your fix didn't work.
Hey um, Im a turtle and Im reading the .txt from the link you gave the color os one specifically. So Im at the step where I have to Double Click "Open This to Proceed" file to start the process. What is this "Open This to Proceed" exactly?
Edit: Never mind. I should've looked more before asking..
IT WORKED!!!!!!! THANK YOU SO MUCH! YOU'RE A LIFESAVER!
koarc lkas said:
IT WORKED!!!!!!! THANK YOU SO MUCH! YOU'RE A LIFESAVER!
Click to expand...
Click to collapse
Now if you want to flash the stock rom you will have to flash firmware first.
flash fw c.xx
wipe 5
flash rom
flash vbmeta disabler
format (type yes)
reboot
You can download the firmware file form here. https://github.com/realme-trinket-organization/firmware_files_RMX1911/releases and the vbmeta disabler from here. https://t.me/r5notes/52
yasir.r said:
Now if you want to flash the stock rom you will have to flash firmware first.
flash fw c.xx
wipe 5
flash rom
flash vbmeta disabler
format (type yes)
reboot
You can download the firmware file form here. https://github.com/realme-trinket-organization/firmware_files_RMX1911/releases and the vbmeta disabler from here. https://t.me/r5notes/52
Click to expand...
Click to collapse
!!! Im having a problem with flashing my stock rom cause it keeps getting bricked. Thank you so much for giving me this!
yasir.r said:
Now if you want to flash the stock rom you will have to flash firmware first.
flash fw c.xx
wipe 5
flash rom
flash vbmeta disabler
format (type yes)
reboot
You can download the firmware file form here. https://github.com/realme-trinket-organization/firmware_files_RMX1911/releases and the vbmeta disabler from here. https://t.me/r5notes/52
Click to expand...
Click to collapse
How do I know my exact build number? I just know that it's realme 5i and it is RMX2030, not those C69 thingies.
koarc lkas said:
How do I know my exact build number? I just know that it's realme 5i and it is RMX2030, not those C69 thingies.
Click to expand...
Click to collapse
I just used the latest version c.73 it worked. I do have to same phone. R5i, RMX2030 with SD665 CPU.
How do I flash the firmware I downloaded from your link? and the vbmeta disabler img is in the firmware-update file, correct?
koarc lkas said:
How do I flash the firmware I downloaded from your link? and the vbmeta disabler img is in the firmware-update file, correct?
Click to expand...
Click to collapse
no no not the image, vbmeta-disabler.zip from here https://t.me/r5notes/52 and flash them in pbrp like you flash the rom.
ohh both zip files, okay
yasir.r said:
no no not the image, vbmeta-disabler.zip from here https://t.me/r5notes/52 and flash them in pbrp like you flash the rom.
Click to expand...
Click to collapse
Upon flashing the firmware zip, my phone keeps getting stuck on bootloop, it doesnt even let me go to recovery mode. It keeps restarting too?
Edit: is this normal??
The tool you gave me to fix fastboot doesnt work anymore :<
koarc lkas said:
Upon flashing the firmware zip, my phone keeps getting stuck on bootloop, it doesnt even let me go to recovery mode. It keeps restarting too?
Edit: is this normal??
Click to expand...
Click to collapse
did you follow the process, properly?? don't tell you flashed just the firmware and nothing else..
yasir.r said:
did you follow the process, properly?? don't tell you flashed just the firmware and nothing else..
Click to expand...
Click to collapse
I only got to step one which you said to get firmware and flash it. I flashed it and my phone rebooted but it keeps restarting. I can still flash images but I cant seem to fix this "reboot loop" and the tool you gave doesnt fix it either. What Im guessing is C73 isnt my firmware version since this phone is years old? Do you know how to delete the firmware so maybe the tool you gave me would work again and I can start over once more?
Edit: Im once again stuck in fastboot btw.
Edit: I fixed the rebooting loop with the stock recovery.bat from the file you gave me but when I do the "open this to proceed" it goes back to rebooting automatically. I still want to remove the C73 firmware though.
Here is a copy of July modems and vbmetas in case anyone needs to reflash their modems due to mismatching May & July patches. Should work for July patched system with May bootloader or some other combo with the july system.
VBMeta should work for any
JULYmodemsbackupN20.zip
drive.google.com
**Note*** please backup your vbmetas before flashing the vbmetas in this archive. According to iKlover these did not work for his July device and had thankfully backed up his own first. I have not had much time to spend on this device lately and likely won't for a while. I was rushing to get this up for anyone in need and may have gotten them mixed up. If anyone can confirm these vbmetas are not July or for a specific device I would greatly appreciate the time and effort***
Also as a side note you can probably just flash your own vbmetas with the disable switches so please be mindful
You're a ****ing saint! Dorothy Mantooth is a saint!
PsYk0n4uT said:
Here is a copy of July modems and vbmetas in case anyone needs to reflash their modems due to mismatching May & July patches. Should work for July patched system with May bootloader or some other combo with the july system.
VBMeta should work for any
JULYmodemsbackupN20.zip
drive.google.com
Click to expand...
Click to collapse
I flashed vbmeta using this command: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
on my July device, and I'm stuck in a bootloop. It boots to recovery only. Any idea how to fix this?
Do you have a backup of stock boot and vbmeta you can restore?
DrScrad said:
Do you have a backup of stock boot and vbmeta you can restore?
Click to expand...
Click to collapse
Yeah, I reflashed and got out of the loop. Thanks for reminding me I made a backup, I didn't remember
iKlover said:
Yeah, I reflashed and got out of the loop. Thanks for reminding me I made a backup, I didn't remember
Click to expand...
Click to collapse
You may be able to flash a blank vbmeta as on other devices. Sorry this happened. I have Soo many backups and was in a rush to get everything backed up on my PC. I can only think that maybe I got the patch dates wrong on these. I will make note..
Also my July device is a sort of Frankenstein at this point and I haven't yet identified the culprit. You should have your carrier boot animation when powering up the phone if everything matches. Mine does not. Just the OnePlus boot animation, circle with the revolving circle/s ..
But everything is working perfectly other than that and the boot animation doesn't bother me so I haven't had the motivation to even look into it yet. I doubt I will even be able to for a while.
iKlover said:
I flashed vbmeta using this command: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
on my July device, and I'm stuck in a bootloop. It boots to recovery only. Any idea how to fix this?
Click to expand...
Click to collapse
Not sure if any of these need flashing as well but if someone wants to back theirs up first and try these maybe it could be of value. Has worked on other manufacturers but I haven't tested on this one nor this device. But:
fastboot flash --disable-verification --disable-verity vbmeta vbmeta.img
Then run fastboot flash --disable-verification --disable-verity vbmeta_system vbmeta.img
Also run fastboot flash --disable-verification --disable-verity vbmeta_vendor vbmeta.img
Or replace vbmeta.img in those last two with the corresponding vbmeta_vendor or vbmeta_system images. You can rename the .bins to .img and flash them if I didn't already rename them in the archive.
If anyone has the time to check this out please do so and post results and/or info if you know whether or not this is necessary or even helpful/possible with this device. I don't want to encourage anything that would cause any issues but if it doesn't work you should just be able to reflash your backups
PsYk0n4uT said:
You may be able to flash a blank vbmeta as on other devices. Sorry this happened. I have Soo many backups and was in a rush to get everything backed up on my PC. I can only think that maybe I got the patch dates wrong on these. I will make note..
Also my July device is a sort of Frankenstein at this point and I haven't yet identified the culprit. You should have your carrier boot animation when powering up the phone if everything matches. Mine does not. Just the OnePlus boot animation, circle with the revolving circle/s ..
But everything is working perfectly other than that and the boot animation doesn't bother me so I haven't had the motivation to even look into it yet. I doubt I will even be able to for a while.
Click to expand...
Click to collapse
These things happen man, no worries. For anyone reading, it's best to back up as soon as you obtain root in case you make a mistake. I prefer Partitions Backup and Restore like the other poster said.