I finally found out where the (boot splashes) are located in MI A3.
Its in the imagefv.elf file found in the stock firmware image.
Extract it via 7zip and you get three files named 0, 1 and 2
Just extract 2 file with 7zip and you will find them
{
"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 have attached the screenshot showing the file contents - sorry for bad markup and the file in zip archive format
I would like if you guys can help to take a look at it and see if replacing them helps to replace the boot splash images
I am willing to test if it doesn't like completely break my device (EDL Mode, I don't have Xiaomi Authorized account to fix it, fastboot brick is okay)
I hope this helps to create a boot splash replacer for our device
It can also be seen in the device if you go to /dev/block/by-name/
Two files maybe representing both the A and B slots are seen
That's interesting...at my end I cannot extract "2" folder...
Anyway, it's not only there where the images are stored....
Check THIS.
And you may want to check THIS thread as well.
Typhus_ said:
That's interesting...at my end I cannot extract "2" folder...
Anyway, it's not only there where the images are stored....
Check THIS.
Click to expand...
Click to collapse
Hmm I don't know why you cant extract it
I just right clicked the elf file, open with, 7zip File Manager and i can browse and extract the contents normally.
Stock 7zip install, nothing fancy, opened like usual archive
I was trying to pinpoint where the images would be and as i saw the partition had image and fv in its name I guessed it stood for the image firmware and tried to open it.
Now if I could just replace the bmp files there with same format and similar size and try to flash it via recovery or fastboot maybe I could see if it replaced the files in xbl or the UEFI boot partition. Since its not modifying xbl directly and changing its hash maybe it wont lead to a permanent brick.
About xbl I rather not modify it, seems to risky. If someone has successfully done it I can follow the method.
Typhus_ said:
And you may want to check THIS thread as well.
Click to expand...
Click to collapse
What version of 7Zip are you running? That's interesting. It seems that version has more features than the one I'm using. From where did you download it?
----EDIT-----
Forget it....I'm running latest version now. Now I'm able to open it.
I came across this info while researching on how to modify bootloaders
There are two levels of unlocking: normal and critical. The basic unlock should cover just about anything most readers will want to do, up to and including flashing a custom recovery, system images, and a modified boot image (useful for Chainfire's "systemless" root). This also allows for flashing officially signed bootloaders. The critical unlock goes a step further and allows users to flash custom bootloaders, which are usually only necessary for removing certain security restrictions or occasionally for adding special features.
Maybe if device is critical unlocked xbl modification is okay? Can anyone shed some light on it?
Some new findings
Looks like someone else also found out about this before me
Sadly no new updates from him or the thread
Also since ours is an A/B device there are 2 bootloader and boot partitions in the phone so there is a chance that if we flash a bad xbl or imagefv file it just causes the device to restore the good one from the other slot if we specify the slot while flashing
Another solution possible i saw on the oneplus forums was about disabling the android qualcomm uefi secure boot, though I don't know how. It is similar to Microsoft's Stupid Uefi secure boot implementation in PC bootloader which prevent installing many linux distros unless disabled.
[HELP]: How to remove "your Device has been unlocked and can't be trusted"
I had rooted my One plus three with TWRP and now everytime I power ON/Restart OR try to switch in Recovery or Fastboot mode then this screen comes "your device has been unlocked and can't be trusted" please help me how to remove this screen...
forum.xda-developers.com
The imagefv is a signed uefi/pi partition though I guess less important than the xbl
On secure boot
VERIFIED / SECURE BOOT
Ensuring a chain of trust from Power ON up to loading of kernel is with the domain of SoC vendor (Qualcomm, Intel etc.) and OEM's. Injecting some malicious or harmful code at any point during booting is made harder to the extent of impossibility.
To ensure a secure booting chain, PBL verifies authenticity of SBL which subsequently verifies integrity of bootloaders (TZ, RPM, DSP, HYP and aboot) so that to avoid loading of unsigned images (boot, recovery, system and others). TZ, after being loaded by SBL also verifies ABOOT using a hardware-based root certificate.
A bootloader with Verified/Secure Boot implementation verifies boot.img or recovery.img (kernel, initramfs and DTB appended to kernel or on second stage of boot.img) by matching their signature with key(s) stored in "OEM keystore" (some partition like CMNLIB, KEYMASTER or with some other name) which itself is signed by OEM. Some vendors allow replacing/appending this keystore with custom one so that custom signed images can be flashed followed by re-locking of bootloader. A simple detail is given here.
At this stage, the chain of trust is handed over to "dm-verity" key stored in boot image initramfs, responsible for "Verified Boot" process of Google/AOSP. Dm-verity (a part of Verified Boot implementing Linux Device Mapper by Google) is a kernel feature i.e. it comes into action after boot image (kernel and ramdisk) is loaded in RAM. It verifies subsequently loading block devices; /system, (/vendor if it exists) and optionally others.
For details see this, this and this.
Google suggests integrating libavb (native code to verify integrity of boot.img) in bootloaders starting from Verified Boot 2.
Got it from this thread
[INFO] BOOT PROCESS: ANDROID vs. LINUX | XDA Developers Forums (xda-developers.com)
It seem it check the integrity of aboot and xbl which means modifying and flashing them over may result in hard brick hic requires xiaomi authorized account and edl flash with firehose or one of no auth patched firehose for the device none of which i haven't been able to find.
There is no mention of imagefv in this so it seem its safe though I don't know for sure
New findings
I have managed to browse and extract both xbl and imagefv files with the help of a few software
UEFI Tool by LongSoft - Release A58 · LongSoft/UEFITool · GitHub - Browse through the ELF files
uefi-firmware-parser by theopolis Release uefi-firmware-parser 1.6 · theopolis/uefi-firmware-parser · GitHub - Extract imagefv file, does not work well with xbl file
imjtool by @morpheus______ imjtool - A tool for unpacking Android boot and system images (newandroidbook.com) - Extract xbl file, does not work well with imagefv file
The imagfv elf consists of a dozen or so RAW images (actually of bmp format)
Although I haven't seen the highlighted one with the black mi logo anywhere in the phone, anyone seen this?
xbl contains these bmp images
There seem to be 3 main differences
xbn has not fastboot image files has a white android one unlocked image instead of a black mi logo showing unlocked in imagefv? and imagefv has a system destroyed image while xbl has a plain black image
Also since imjtool has problems with imagefw file, i suspect it is not a regular/as important file as xbl
I just don't know how to repack imagefw with custom images and flash it
Also I compared the partition layout of my old Redmi 5 to that of Mi A3
Redmi 5 Layout
And confirmed from my side and this thread [GUIDE][Redmi 5] How to change Splash Screen (Boot Logo) for Redmi 5 | XDA Developers Forums (xda-developers.com) that it stores its splash in splash.bin and that imagefv is unique to our and possibly other uefi devices
New Updates on Findings
Short Ver. : Secure Boot and UEFI is not a Good Combo for User Customization
Long Ver.
Comparative Investigations
1. Mi A2
When the Mi A2 xbl is compared with Mi A3 one there is an absence of images except for a snapdragon logo and battery bitmaps
There is also no imagefv file and the splash.img format is used for bootlogo
2. When comparing the A3 to CC9e, its non Android One version, both of their imagefv and xbl files are similar
But there is some differences
The CC9e imagefv doesn't contain the androidone logo (replaced by mi logo)
The xbl file of CC9e contains a much more beautiful, in my opinion boot splash (black with mi logo and powered by android slogan)
This confirms that boot splash may indeed be possibly stored in xbl as there is no unlocked boot logo in imagefv which is bad news as we cant modify signed ELF images without modfying its signature
And as i saw in the oneplus forums and this info thread even changing a single letter in bootloader that is xbl or aboot to modify it can result in a hard brick device in edl mode
bootloader / qfuses / ARB - how not to brick your phone for funsies v1 | XDA Developers Forums (xda-developers.com)
I also checked out thr Redm Note 8 xbl and imagefv as i saw that in that devices too no splash.img was found, well its more bad news
The Note 8 has all its images in xbl and not in imagefv
I don't even know the purpose of imagefv any more
Only info I could find was this
[F1 geek stuff] UFS information, details about LUNs and partition scheme | XDA Developers Forums (xda-developers.com)
imagefv = lzma compressed bitmaps (battery), signed part of uefi
I am now going to investigate the Poco F1 xbl and other files
Only hope now is if we can introduce a fake logo.bin or splash.img and hope that the files there is given preference over those in imagefv or xbl
Another way is something like HackBGRT for PC's, using another EFI program to load another image at boot
HackBGRT/README.md at v1.5.1 · Metabolix/HackBGRT · GitHub
Or else we can hope that in 2-3 years this will also be cracked and hacked open by some method (disable secure boot?) and we can modify these files.
Most of Xiaomi's, Google's and other companies new mobiles are coming with there boot splashes hard-coded into xbl like this.
Thanks for your feedback on this matter. Keep it up Bro.
Related
{
"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"
}
Supported devices :
sofia
sofiap
sofiap_ao
sofiar
rav
rav_t
Download (GApps included)
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot -w (mandatory if coming from stock, warning tho : it will erase all your data)
UPDATE
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram support group : https://t.me/Motorola_G_Stylus
20200821 Changelog :
- Add support for g8/g fast
- Add LED support
- Add selinux enforced for all
- Safetynet should pass for all devices (can't check my self, let me know)
- Fix crash when turning off wifi hotspot
XDA:DevDB Information
OmniROM, ROM for the Moto G Stylus
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: 2.3.x Gingerbread
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-08-28
Created 2020-08-28
Last Updated 2020-08-28
2.3.x Gingerbread?
Just installed on my device, works great first try, only thing I've found to not work is Moto Audio with any sort of headphones, works with internal speaker tho. great work thanks!
googl-fi sofiap cannot flash to system
I am unable to flash to the system. It will not let me delete the super or system file. not sure what to do tried everything that is listed on the flash gsi. anyone with some help
lightningdude said:
2.3.x Gingerbread?
Click to expand...
Click to collapse
Typo, dude. F
rooted?
is this rom rooted?
vache said:
Supported devices :
sofia
sofiap
sofiap_ao
sofiar
rav
rav_t
Download (GApps included)
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot -w (mandatory if coming from stock, warning tho : it will erase all your data)
UPDATE
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram support group : https://t.me/Motorola_G_Stylus
20200821 Changelog :
- Add support for g8/g fast
- Add LED support
- Add selinux enforced for all
- Safetynet should pass for all devices (can't check my self, let me know)
- Fix crash when turning off wifi hotspot
XDA:DevDB Information
OmniROM, ROM for the Moto G Stylus
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: 2.3.x Gingerbread
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-08-28
Created 2020-08-28
Last Updated 2020-08-28
Click to expand...
Click to collapse
stolirocks said:
is this rom rooted?
Click to expand...
Click to collapse
Nope.
Although not "rooted" you can root after installation just like you would with stock.
Thank you for the ROM. First time using OmniRom and loving it so far. I have not run into any issues so far. Even on t-mobile, my WiFi calling, visual voicemail and text messages all are working without any issues.
Will you be releasing a version with just MicroG instead of gApps? I ended up just uninstalling all the gApps anyways, but just curious.
Keep up the great work!
GApps Dilemma
I am really looking forward to not having Gapps on this device, I haven't installed yet due to this, and wonder. Is this OpenGApps implentation removable using the same instructions as if it were installed manually after the CFW was flashed? Also, if it is not too much extra work, could you post a non GApps build?
Thanks for the hard work!
griz.droidx said:
Although not "rooted" you can root after installation just like you would with stock.
Click to expand...
Click to collapse
I tried rooting with the latest & second latest SuperSU flashable zip, but it didn't work. Do you know what build I could use?
.Solotato said:
I tried rooting with the latest & second latest SuperSU flashable zip, but it didn't work. Do you know what build I could use?
Click to expand...
Click to collapse
Greetings Solotato and Moto/Android community ,
I know this post is long excessively but hopefully it'll get the point across. Please don't think I'm talking down to you or anyone else. This whole process had me baffled at first as well and I've used others work to root and rom fur years. I've used Linux on the desktop by dual and even triple booting (Nix,Xpor2K, and 98 for old hardware slash gaming support) I even wrote a config for a guy's app called js2mouse to use 2 pointers at the same time in X(wanted to use my old logitech wingman cordless as a remote. But I'm no expert and still consider myself a little above novice. This isn't meant to offend anyone. Shew (the us is just too politically correct)
You can use twrp i think with magisk. BUT...im pretty sure i flashed twrp once in the recovery bootloader before but nothing else would take and twrp didn't function correctly.
I agree with many others now that it's easier to put a copy of the boot image on your device after installation. It's simple really
Just boot your device,
Enable developer options first thing then adb, then you can connect with a usb cable and approve adb access in your phone.
Copy the boot image to your phone and use the latest official magisk to patch the boot image. In magisk pick install then pick image, you pick your boot image which is then patched and renamed magisk_patched or similar.
It'll be in your downloads folder. Move it back to your pc, the patched one of course, and then just
fastboot flash boot magisk_patched.img
A TIP if you're new to the command line/powershell(win) or terminal(nix/bsd/mac (which is based on bsd)You can even use the up arrow if you dunt want to retype the commands then just replace boot.img with magisk_patched.img just start typing magis then hit tab and it'll complete it for you..
All this looks complicated but trust me after you do it a few times you'll be doing it in a minute or two.
Good luck take your time and read everything you can find. Don't forget to ask the command line for --help! You can find help in a jiffy that way.
Example
fastboot --help i think is the syntax i can't see it on my phone but there's a space between the two dashes and the command your asking for help. And for more details help is included in Linux with man pages. Those are handy in a pinch.
Even though I've done this since the droidx days on many phones, it still took me a lot of research and reading to get this new a/b partitioning and fastboot stuff down to where i can do it quickly.
Read and search these threads you'll be more likely to get answerers from xda members if they can tell you've been reading up on it.
Good luck!
Practice practice practice. That's the advice my uncle gave me on shooting a bow (instinctive or without sights) and he was right. This applies to everything in life.
Anyway I've preached enough. I know it's a long post but hopefully you and others who are relatively new to these moto's will get some help here.
Don't forget to thank the developers and others who made all this coolness possible for us who benefit from
If i helped any at all or you enjoyed my way too many useless details style, please hit thanks. I appreciate that. Sorry for the delay in posting I'm still setting up my most recent rom and I've doing a lot of stuff outside my home before winter.
Sent from my Moto G Stylus using XDA Labs
Sorry guys that was waaaaay too long.
Sent from my Moto G Stylus using XDA Labs
Could anyone point me in the right direction for recompiling this rom's kernel with a different config? I'm looking to poke around & try to get USB OTG/ACA mode to work (i.e. have the phone charge as well as use a usb device, like a mouse/keyboard/storage), which is apparently possible by setting CONFIG_USB_MSM_OTG and CONFIG_USB_MSM_ACA.
I've never compiled a kernel for another arch before, and I assume I need a toolchain that targets arm64 to begin with - I've also never really built anything for android before, and all the guides I've found thus far seem to either be for a specific device or building an entire system image, which seems to be too much - I'm given to understand I can replace the kernel image in boot.img by itself with a tool like mkbootimg.
Any help with where to start would be appreciated, thanks!
My Screen isn't working anymore... using an OTG to move around....
It's the touch screen
Another user asked this previously without any response ... Could you post a degoogled Omni ROM without gapps? Or give any advice how to remove it ? You were the one to put it all together so surely for you it must be easy removing it? As for me, I've been stuck.
Hi I am really struggeling here ... Everytime I try to flash system it ends with
writing 'system_b' 2/3...
FAILED (remote: Operation not permitted)
my bootloader is unlocked and I am in fastbootd.
I so far tried:
- other USB cables
- other ROM´s
- factory wiping
- flashing stock image again (which does work in both fastboot and fastbootd)
- reflashing recovery with stock one
- relocking and unlocking
- booting in to fastbootd via command and buttons
- diffrent minimal adb and fastboot versions
anyone have any ideas what I am doing wrong?
ianspy1 said:
Hi I am really struggeling here ... Everytime I try to flash system it ends with
writing 'system_b' 2/3...
FAILED (remote: Operation not permitted)
my bootloader is unlocked and I am in fastbootd.
I so far tried:
- other USB cables
- other ROM´s
- factory wiping
- flashing stock image again (which does work in both fastboot and fastbootd)
- reflashing recovery with stock one
- relocking and unlocking
- booting in to fastbootd via command and buttons
- diffrent minimal adb and fastboot versions
anyone have any ideas what I am doing wrong?
Click to expand...
Click to collapse
I am in no way a professional like other members here who probably can give you better advice but I was more successful when I downloaded platform tools version 26.0.0. I wasn't successful on my device but after using a older version I was able to get a different set of errors. But I also at the end was unable to flash. Maybe this will help you ?
gatorz_4z said:
I am in no way a professional like other members here who probably can give you better advice but I was more successful when I downloaded platform tools version 26.0.0. I wasn't successful on my device but after using a older version I was able to get a different set of errors. But I also at the end was unable to flash. Maybe this will help you ? My hope is that with that version you will be successful? Another person told me to redownload the ROM and try with a fresh one.
Click to expand...
Click to collapse
Gotta love how unsupported this ROM is... Or just busy dev...
Unlocked Firmware for JioFi 3 JMR540 & JMR541
Disclaimer
I am not responsible for any kind of damage to your device.
Use this firmware at your own risk
Post is for educational purpose only.
ONLY FOR JMR 540 & JMR 541
I was able to dump and reverse engineer JioFi 3's firmware to see if I can unlock the SIM restrictions. JioFi 3 is designed by Foxconn it uses generic firmware. Unlocking took time though. Tested with Vi, Airtel.
UPDATE 17-10-21: Jio pushed a firmware update which is locking boot loader. If your device is not updated yet it is advised to re-flash your firmware with patched image given below which basically disables auto updates. If you're already locked out, currently there's no easy fix for that.
If you haven't used your device from a long time or you're still on lower or equal version than below it is advised not to use JioFi with SIM, flash this firmware first if you want to test SIM unlock.
Guide
Make sure you're on same or lower firmware version
JMR 540 - FXN_JMR540_R6.16
JMR 541 - FXN_JMR541_R3.10
1. Locate your device model and download the respective Firmware and extract it to a known location
JMR540_unlocked_patched_system.zip
JMR541_unlocked_patched_system.zip
2. Install drivers and tools (skip if already installed)
Install Fastboot drivers ( google it for mac and linux it's easy to find)
Install Fastboot ( google it for mac and linux it's easy to find)
3. Prepare device
Remove battery from JioFi 3
Locate reset pin hole button
Lay down JioFi 3
Use Paper Clip / SIM Ejector Tool to press button inside (using sharp object is not recommended)
Keep pressing button down and insert USB cable
Release button as soon as all the LEDs in Display turns RED. This means device is in boot loader mode
4. Flashing Unlocked Firmware
Open adb and fastboot tools terminal
Enter following to check if device is connected
fastboot devices
It will return something like this
baxxxxx fastboot
This means device is connected. If your device doesn't show up here please check drivers in Device manager
Now first erase the system partition
fastboot erase system
It will return something like this
erasing 'system'...
OKAY [ 1.104s]
finished. total time: 1.105s
Now flash the firmware
fastboot flash system "D:\system.img" ( replace path )
It should return something like this
sending 'system' (34306 KB)...
OKAY [ 1.276s]
writing 'system'...
OKAY [ 9.462s]
finished. total time: 10.741s
Now send reboot command to device
fastboot reboot
You'll notice device will reboot normally now you can unplug the cable.
Congratulations your device is now unlocked and you can reinsert battery and another SIM for testing.
Firmware will take long time than usual to boot do not panic.
4. Changing APN
Insert SIM connect with JioFi 3 wait it to intialize
Open Web UI from browser (http://jiofi.local.html/)
Now login (default username/pwd is administrator/administrator)
In Network Tab you'll find setting for changing APN
Put it on manual and enter "internet" as APN (without quotes)
Hit apply/save device will reboot again automatically and it'll auto connect
Just wait patience is the key here it'll connect.
If something goes WRONG or you want to UNDO you can re flash original firmware which is provided in this post.
Original backup
JMR_540_original_system.zip
JMR_541_original_system.zip
FAQs
Q. My device is not visible in fastboot devices
A. Confirm driver installation a faulty cable can also be the issue.
.
Q. Everything went well but still no changes in dashboard
A. After successful flash if you still don't see the changes your device is probably booting from recovery partition. Try flashing recovery partition by
fastboot erase recoveryfs
fastboot flash recoveryfs "D:\system.img"
.
Q. After resetting device from pin hole button it shows INVALID SIM.
A. This is supposed to happen just reboot the device it'll work again.
.
Q. Can I undo all this and get back to original firmware
A. Yes just flash the original firmware provided in post and reset the device.
.
Q. I 'accidentally' flashed my recovery and boot partition
A. Well accidentally I've backed up recovery and boot download from below
1. JMR540_boot_recovery.rar
2. JMR541_boot_recovery.rar
.
Q. FAILED: (remote: Image is locked) issue while erasing/flashing image
A. Jio recently pushed an firmware update which re-locks simlock and bootloader which basically means you can't flash unsigned/custom firmware. Currently there is no fix.
Mentions:
Thanks to Karuppusamy for testing it on JMR541.
What about JioFi 2, 4, 5, 6?
Reverse Engineering takes lot of time and coffee. Until I get physical access to device I won't be able to unlock it. I'm constantly searching them on OLX as soon as I get hands on I'll surely try to RE and unlock it. I'll update the same here if there is no update here at the time of your reading then I haven't got the device yet so please don't spam for update hope you understand that I don't get anything by doing these things, I do it for liberation of locked hardware to meet it's real destiny and of course for the people. I also have a day job so no I cannot guide or teach you, hope you understand why.
For Devs:
JMR_540_FLASH_DUMP.rar
Reserved
successfully unlocked my jiofi 3 JMR541. tested with voda and its working well and good. Thanks a ton for this bro.
I was late in checking this thread and got shipped airtel unlocked mifi from home.
sksinha said:
successfully unlocked my jiofi 3 JMR541. tested with voda and its working well and good. Thanks a ton for this bro.
I was late in checking this thread and got shipped airtel unlocked mifi from home.
Click to expand...
Click to collapse
Can you show us dashboard screenshot. This will help other users to verify
abhimortal6 said:
Can you show us dashboard screenshot. This will help other users to verify
Click to expand...
Click to collapse
...
Nice, enjoy!
abhimortal6 said:
Nice, enjoy!
Click to expand...
Click to collapse
bro is unlocking more 4g bands or manual selection of bands can be done ?
sksinha said:
bro is unlocking more 4g bands or manual selection of bands can be done ?
Click to expand...
Click to collapse
Totally possible even 3G but it can't be done through WebUI it'll requires shell access.
Totally working! thanks a ton a bro <3
srbhsngwn said:
Totally working! thanks a ton a bro <3
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"
}
Great
..
myapky said:
JMR540 ERROR
Click to expand...
Click to collapse
you haven't properly specified the address of system.img Please give the complete path
srbhsngwn said:
you haven't properly specified the address of system.img Please give the complete path
Click to expand...
Click to collapse
Fixed issue.
myapky said:
there is a issue with JMR540, however I have successfully flashed JMR541 file on friends JioFi 3.
There is definitely a issue with JMR540 system.img file. request @abhimortal6 to check the file and reupload.
I have added a device info details for JMR540
Click to expand...
Click to collapse
This issue is not related to flash file as I own JMR 540 and it's been tested on multiple devices (refer attached image). "Not working" and "Not flashing" are two different things.
"flash write error" is a sign of bad emmc/nand, bad partition table can also be the cause. Please first try with original firmware and collect information by different permutations (re-downloading image, erasing system before flashing etc) before spamming.
abhimortal6 said:
This issue is not related to flash file as I own JMR 540 and it's been tested on multiple devices (refer attached image). "Not working" and "Not flashing" are two different things.
"flash write error" is a sign of bad emmc/nand, bad partition table can also be the cause. Please first try with original firmware and collect information by different permutations (re-downloading image, erasing system before flashing etc) before spamming.
View attachment 5326935
Click to expand...
Click to collapse
I am not spamming i am facing issue so I mentioned at XDA. I am facing 'flash write error' with the original system.img file too. Unable to flash img files.. Any solution to that ?
myapky said:
I am not spamming i am facing issue so I mentioned at XDA. I am facing 'flash write error' with the original system.img file too. Unable to flash img files.. Any solution to that ?
Click to expand...
Click to collapse
A single post with all the details in it would be sufficient.
As stated in previous post please try the following.
Try flashing original firmware first
Try erasing system partition ( fastboot erase system)
Try re downloading image
If you're getting flash write error in original firmware too then you're nand is probably fried.
try flashing recoveryfs partition
Bash:
fastboot flash recoveryfs "system.img"
abhimortal6 said:
A single post with all the details in it would be sufficient.
As stated in previous post please try the following.
Try flashing original firmware first
Try erasing system partition ( fastboot erase system)
Try re downloading image
If you're getting flash write error in original firmware too then you're nand is probably fried.
try flashing recoveryfs partition
Bash:
fastboot flash recoveryfs "system.img"
Click to expand...
Click to collapse
nand was dead...due to all day work on JioFi, now all good thanks for help.
abhimortal6 said:
Unlocked Firmware for JioFi 3 JMR540 & JMR541
Disclaimer
I am not responsible for any kind of damage to your device.
Use this firmware at your own risk
Post is for educational purpose only.
ONLY FOR JMR 540 & JMR 541
I was able to dump and reverse engineer JioFi 3's firmware to see if I can unlock the SIM restrictions. JioFi 3 is designed by Foxconn it uses generic firmware. Unlocking took time though. Tested with Vi, Airtel.
Guide
Make sure you're on same firmware version
JMR 540 - FXN_JMR540_R6.16
JMR 541 - FXN_JMR541_R3.10
If not please use the device for sometime it'll autoupdate.
1. Locate your device model and download the respective Firmware and extract it to a known location
JMR540_unlocked_system.zip
JMR541_unlocked_system.zip
2. Install drivers and tools (skip if already installed)
Install Fastboot drivers ( google it for mac and linux it's easy to find)
Install Fastboot ( google it for mac and linux it's easy to find)
3. Prepare device
Remove battery from JioFi 3
Locate reset pin hole button
Lay down JioFi 3
Use Paper Clip / SIM Ejector Tool to press button inside (using sharp object is not recommended)
Keep pressing button down and insert USB cable
Release button as soon as all the LEDs in Display turns RED. This means device is in boot loader mode
4. Flashing Unlocked Firmware
Open adb and fastboot tools terminal
Enter following to check if device is connected
fastboot devices
It will return something like this
baxxxxx fastboot
This means device is connected. If your device doesn't show up here please check drivers in Device manager
Now first erase the system partition (Skip for JMR 540 )
fastboot erase system
It will return something like this
erasing 'system'...
OKAY [ 1.104s]
finished. total time: 1.105s
Now flash the firmware
fastboot flash system "D:\system.img" ( replace path )
It should return something like this
sending 'system' (34306 KB)...
OKAY [ 1.276s]
writing 'system'...
OKAY [ 9.462s]
finished. total time: 10.741s
Now send reboot command to device
fastboot reboot
You'll notice device will reboot normally now you can unplug the cable.
Congratulations your device is now unlocked and you can reinsert battery and another SIM for testing.
Firmware will take long time than usual to boot do not panic.
4. Changing APN
Insert SIM connect with JioFi 3 wait it to intialize
Open Web UI from browser (http://jiofi.local.html/)
Now login (default username/pwd is administrator/administrator)
In Network Tab you'll find setting for changing APN
Put it on manual and enter "internet" as APN (without quotes)
Hit apply/save device will reboot again automatically and it'll auto connect
Just wait patience is the key here it'll connect.
If something goes WRONG or you want to UNDO you can re flash original firmware which is provided in this post.
Original backup
JMR_540_original_system.zip
JMR_541_original_system.zip
FAQs
Q. My device is not visible in fastboot devices
A. Confirm driver installation a faulty cable can also be the issue.
.
Q. Everything went well but still no changes in dashboard
A. After successful flash if you still don't see the changes your device is probably booting from recovery partition. Try flashing recovery partition by
Bash:
fastboot flash recoveryfs "system.img"
.
Q. After resetting device from pin hole button it shows INVALID SIM.
A. This is supposed to happen just reboot the device it'll work again.
.
Q. Can I undo all this and get back to original firmware
A. Yes just flash the original firmware provided in post and reset the device.
Mentions:
Thanks to Karuppusamy for testing it on JMR541.
Click to expand...
Click to collapse
Hi, i just read ur article on unlocking jiofi 3 and that looked amazing.But i have a jiofi JMR815 and have been looking for help to unlock it from a couple of years.But till date only your post looks promising and i ask yourhelp in helping me unlock my JioFi JMR815.Kindly consider helping me.Also i created an account in XDA just to ask your help
View attachment 5327245
View attachment 5327247
View attachment 5327249
View attachment 5327251
This is completely genius! I am now able to use Airtel sim on my JioFi! Thanks!
Ok so after following a few guides to unlock bootloader on my LM-G710 (Judyln), now I want to PROPERLY install TWRP, with full access to all partitions so I can flash a custom ROM.
I can now root with Majisk.
It seems I can only install TWRP using Majisk Manager apk, if I use QFIL or fastboot (after deleting lafs) to flash TWRP I get bootloops.
I've followed this guide for TWRP and DM Verity/Disableforceencryption:
LG-V35-Tinkering-Instructions/README_EN.MD at master · kaneorotar/LG-V35-Tinkering-Instructions
Unleash your LG V35 ThinQ. Contribute to kaneorotar/LG-V35-Tinkering-Instructions development by creating an account on GitHub.
github.com
And this is the main guide I followed to unlock bootloader:
[GUIDE] Guide to unlock bootloader for every LG SDM845 except G710TM (With PHOTOS)
IMPORTANT: NEVER ERASE THE ENTIRE FLASH (IT WILL BRICK YOUR PHONE **STILL CAN BE RECOVERED**) IMPORTANT: FOLLOW ALL THE STEPS IN ORDER TO UNLOCK BOOTLOADER SUCCSSEFULLY; DISCLAIMER: I AM NOT RESPONSIBLE IF YOUR PHONE BRICKS! YOU ARE FOLLOWING...
forum.xda-developers.com
I'm having issues with TWRP not able to do anything in terms of mounting internal storage.
Also the 'system' partition is missing.
It can't mount anything, internal storage shows 0mb, and I can't wipe or flash anything!
I'm at the step in the first guide where I'm supposed to format data after flashing DM-VERITY where I get errors, it fails and I get a TON OF ERRORS
(The guide says its normal to get ONE error 'unable to unmount vendor' upon flashing DM-VERITY)
Also, a big red flag that I noticed is when loading TWRP for the first time, its supposed to ask me permission to swipe to 'allow system modifications', which didn't happen in my case.
So I think its something to do with LG and I've confirmed the bootloader is unlocked by going into fastboot.
Now when booting into fastboot (after deleting lafs) I got two different fastboot screens in different circumstances, one had red text which says 'unlocked', the other had green/blue text with instructions how to unlock bootloader.
(TWRP partition log below).
Please help! This is driving me crazy and I spent days on this phone!
{
"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"
}
Glad to see so many people willing to help...:/
Ok so I don't think TWRP has access to system modifications, because it doesn't ask me to allow system modifications when loading TWRP like it should. Can't proceed!
Okay you duplicated but if ya need help ill be here.
Kenora_I said:
Okay you duplicated but if ya need help ill be here.
Click to expand...
Click to collapse
Ok thanks, I'll make sure I don't duplicate in the future, I appreciate the heads up.
So my biggest issue here is I don't seem to be able to format any partitions within TWRP for some reason, I confirmed the bootloader is unlocked by [ a) device fastboot screen, b) developer options c) fastboot command]
However, in TWRP when I proceed switch slots (a or b) it says 'failed' but when I return to the TWRP reboot menu it lists the slot I tried to change to, so is it the version of TWRP I am using is just broken and I should try another one?
Problem is there's no official TWRP for my model.
I got the same model as you i just gave up installing twrp to this device bcs encrypted storage and no bootloader fastboot access with volume down button
kunarbale said:
I got the same model as you i just gave up installing twrp to this device bcs encrypted storage and no bootloader fastboot access with volume down button
Click to expand...
Click to collapse
Yeah I gave up too, I turned to somebody who might be able to do it.
LG locks their phones so people won't uninstall their apps, and this model is quite a doozy!
kunarbale said:
I got the same model as you i just gave up installing twrp to this device bcs encrypted storage and no bootloader fastboot access with volume down button
Click to expand...
Click to collapse
Just take off your password or pin.
Data is encrypted usually when you have a lock screen password.
LameMonster82 said:
TWRP 3.3.1-0+ for the LG G7 ThinQ
Warning: This TWRP Recovery is only useful for installing custom ROMs.
Currently there's no way to use this recovery on stock in any meaningful way without future addons
(Data partition cannot be read because of LG default encryption)
You cannot install or backup anything while you have LG Encryption enabled. A future addon can disable it.
<-- Requirements
An Bootloader unlocked LG G7 ThinQ by any means. (official or unofficial) (G710TM Models are impossible to be supported, sorry)
More information on officially unlocking the LG G7 here: https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
Running minimum LG Stock Android 9 Pie (AOSP GSI does not count)
A PC and ADB + Fastboot
The temper to read twice
<-- Needed files
You only need this boot image:
https://drive.google.com/open?id=1FcIBNfL3_72cQwuxd2TyZSjnC-ItnNTt
For developers who want to build their own TWRP Boot image here's the device-tree for it
https://github.com/LameMonster82/android_device_lge_judyln-twrp
<-- Installation
Note: This TWRP is only temporarily (it does not overwrite the bootimage). When you reboot it will dissapear and you will need to redo the fastboot command.
You're done. Now you can use TWRP to install custom ROMs
------------------------------------------------------------------------------------------------------------------------
Legacy tutorial. Do not use unless you use TWRP older than Feb 2020.
↓
Code:
[SIZE="5"][B][I][CENTER]<-- Needed files[/CENTER][/I][/B][/SIZE]
[LIST]
[*]You only need this boot image:
[url]https://drive.google.com/open?id=1n2wKdwARddx_KCIdLi10KawY_THlcRi4[/url]
[*]For developers who want to build their own TWRP Boot image here's the device-tree for it
[url]https://github.com/LameMonster82/android_device_lge_judyln-twrp[/url]
[/LIST]
[SIZE="5"][B][I][CENTER]<-- Installation[/CENTER][/I][/B][/SIZE]
[QUOTE][SIZE="3"][B]Step 1: Enter Fastboot mode[/B][/SIZE]
[LIST]
[*]Connect your phone to your PC with a USB Cable
[*]Restart the phone
[*]While the phone is restarting hold Volume down button.
[B]Note[/B]: Make sure you hold Volume down button before you see the [U][B]black and white[/B][/U] "LG G7 ThinQ" text
If you see the red LG Logo you either messed up or you don't have access to fastboot mode witch is another problem i can't solve easily.
[*]If done correctly you should be in Fastboot now :)
[/LIST]
[SIZE="3"][B]Step 2: Install the boot image[/B][/SIZE]
[LIST]
[*]Open the command prompt or your terminal (depending on what PC Platform you are)
[*]Type:
[/LIST]
[CODE]fastboot flash boot_a [B][TWRP Boot image location] --set-active=a[/B]
The best way you can set the TWRP Boot image location is to manually "drag and drop" the file itself in your command prompt
Also make sure you "drag and drop" the TWRP Boot image before you type --set=active=a
Don't forget --set-active=a has 2 little lines at the beginning. No space between them.
Step 3: Enter Recovery mode
Restart the phone (using power button if you're still in fastboot)
Before the phone turns off hold Volume down and power button
The moment you see the black and white "LG G7 ThinQ" Text start clicking the power button as much as you can without letting the Volume down button.
If done correctly you should see a white screen with "Factory reset" text on top.
If you done step 2 correctly clicking yes on both prompts on the phone will get you to TWRP
For people who still have trouble getting into recovery mode here's a visual example of how to enter recovery mode (youtube)
Note: You don't have to be in system. Rebooting from bootloader will still work
Click to expand...
Click to collapse
Congratulations you now have TWRP Recovery on your LG G7 ThinQ :highfive:[/CODE]
Join our Telegram Group here:
>> t.me/lgg7thinqmain <<
I would like to thank:
@Sellerie_ and @J0SH1X for their help on the TWRP Project for LG G7 ThinQ
Here be dragons!
This the TWRP you used?
This is temporary but try to use this and check.
Kenora_I said:
Just take off your password or pin.
Data is encrypted usually when you have a lock screen password.
Click to expand...
Click to collapse
first off do you have the LG G7 AWM model ?
for newer android system vendor is encrypted by default with or without password/lockscreen, even when I can boot up to twrp and able to format system to install dm verity disabler you can't use stock firmware anymore and this AWM canadian model is pain in the arse because you cant just enter bootloader mode with button combination the culprit is because bootloader partition doesnt exist the only way is to trigger it using lg v35 boot.img
Kenora_I said:
Congratulations you now have TWRP Recovery on your LG G7 ThinQ :highfive:[/CODE]
Join our Telegram Group here:
>> t.me/lgg7thinqmain <<
I would like to thank:
@Sellerie_ and @J0SH1X for their help on the TWRP Project for LG G7 ThinQ
Here be dragons!
This the TWRP you used?
This is temporary but try to use this and check.
Click to expand...
Click to collapse
I used the same version from the github link
https://github.com/kaneorotar/LG-V35-Tinkering-Instructions/blob/master/README_EN.MD
I don't have a screen lock password, and I unlocked bootloader with v35 from this post
[GUIDE] Guide to unlock bootloader for every LG SDM845 except G710TM (With PHOTOS)
IMPORTANT: NEVER ERASE THE ENTIRE FLASH (IT WILL BRICK YOUR PHONE **STILL CAN BE RECOVERED**) IMPORTANT: FOLLOW ALL THE STEPS IN ORDER TO UNLOCK BOOTLOADER SUCCSSEFULLY; DISCLAIMER: I AM NOT RESPONSIBLE IF YOUR PHONE BRICKS! YOU ARE FOLLOWING...
forum.xda-developers.com
kunarbale said:
first off do you have the LG G7 AWM model ?
for newer android system vendor is encrypted by default with or without password/lockscreen, even when I can boot up to twrp and able to format system to install dm verity disabler you can't use stock firmware anymore and this AWM canadian model is pain in the arse because you cant just enter bootloader mode with button combination the culprit is because bootloader partition doesnt exist the only way is to trigger it using lg v35 boot.img
Click to expand...
Click to collapse
Yeah its AWM Canadian model. I unlocked bootloader with the instructions here:
[GUIDE] Guide to unlock bootloader for every LG SDM845 except G710TM (With PHOTOS)
IMPORTANT: NEVER ERASE THE ENTIRE FLASH (IT WILL BRICK YOUR PHONE **STILL CAN BE RECOVERED**) IMPORTANT: FOLLOW ALL THE STEPS IN ORDER TO UNLOCK BOOTLOADER SUCCSSEFULLY; DISCLAIMER: I AM NOT RESPONSIBLE IF YOUR PHONE BRICKS! YOU ARE FOLLOWING...
forum.xda-developers.com
So there no hope for this model? What about this guide: https://androidbiits.com/root-lg-g7-thinq-lmg710awm-lm-g710awm-easily/. I guess that's just a quick guide for rooting not really addressing OP's desire to have TWRP installed.
[Unbrick Realme 7 PRO RMX2170 128GB with NFC - softbrick - bootloader unlocked UI 1.0 - Android10]
This tutorial works only in soft brick devices, for hardwre bricks only flashing with MSM Download and it I don't know how this works.
I don't know if this tutorial will works with other devices.
Try this if you don't have another way.
------------------------------------------------------------------------------------------------------------------------------------------
- I not responsable for your decision to try. -
- I'm not responsible for your device (hard brick or other things that might happen) -
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
- IMPORTANT NOTE -
- Unlocked Bootloader devices only (It's very important) Only Android 10 -
- If your device have locked bootloader only realme repair shop can help you, or flashing with MSM -
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Let's Start
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Flash the PBRP 3.0
[RECOVERY][UNOFFICIAL][RMX2170][v3.0.0] Pitch Black Recovery [10/12/20]
/* *Disclaimer * * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
**** Don't change the name this image to recovery using anyway
PBRP-RMX2170-3.0.0-20210113-1340-UNOFFICIAL.img****
Download the ROM (of the official channel, I'm using RMX2170 A.41 PU) ozip format
Software Update - realme (India)
Update the latest software version on your realme phone.
www.realme.com
Download the rom OFP format
Search on google for your ROM, generally this type have 7GB
Put the rom ozip in device (external sdcard) the rom can be send to device for USB conection normally.
In PBRP goes in wipe menu and select Data (It's very important too) change partition Ext2 wait finish and select again to ext4 to remove any block on /Data partition.
Reboot menu and select reboot to recovery.
-----------------------------
Now proceed to PC
Download and opens the MCT ofp extract tool to extract the ofp to files img. (Only works on windows, in Linux use a VM)
The user nirmago alerted me over a virus in this file, thanks nirmago. Proced with caution with file. I used a new way to decrypt the ofp files
oppo_decrypt
Is free and developed in python, works very well in linux and I believe what this not have worms.
Is very simple to use
choose the OFP file
select a ouput folder to extract the files
and click on EXTRACT and wait finish.
*************
Important: After extract you will have 124 files in folder and this folder have 11.8GB.(See in baseboard of window). And the super file have 8GB. like picture below. See in pictures below, the first image to show how many files have in folder and the second picture the size of super file, see too what I have only one Super file.
Image 1 - 124 files extract and the folder with 11.8Gb. See in baseboard of window.
{
"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 2 - The Super file have 8Gb.
*************
Meanwhile remove the sd of your device (you don't need shutdown the device only remove)
Put the sdcard on pc and copy the folder of generate with MCT extract tool folder to root (Not move this folder to device for USB bcz some files not will be copied)
Put the ozip too (download the ozip that you had before RMX2170XX_11_A.XX)
Remove sdcard of your PC and put again on device. (Here I recommend security removal with using windows 10 or 11)
-------------------------------------
Proceed again on device
After you puted the sdcard on device goes to Mount menu in PBRP and select mount your external sd again.*
And the PBRP will reconect the sdcard.
* if you shutdown to remove the sdcard it's not necessary.
Open the folder that you copied (generated by MCT) on sdcard
Open flash menu and seek for img files above:
Boot.img
Super.img (This file is the key to recovery the system)
Recovery.img
Persist.img
Vbmeta.img
Vbmeta_system.img
Vbmeta_vendor.img
Touch on each one at a time, select the respective name on selection box and flash.
Now reboot to system, the system will crash on load, but not have bootloop, don't worry it's normal.
Reboot to bootloader again with procedure above.
*** vol+ + power at device reboot and fastly push vol- right after the device vibrate ***
In bootloader.
Now put de PBRP image again with the command above. Sometimes the device keeps restarting constantly
be quick to put the command.
fastboot flash recovery PBRP-RMX2170-3.0.0-20210113-1340-UNOFFICIAL.img
In PBRP
Wipe data, cache, dalvik
Install the ozip file that you downloaded before
and then the system will goes normal and the device is live again, [in my case the wifi not working after start system]
If you wanna the official recovery again, or have problems like wifi not works.
On PC open a terminal inside the folder created by MCT with the uncompressed OFP rom and use the commands above:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Press vol- at show up on screen reboot to recovery and will have the official recovery again
*If you have the wifi issue like me put the ozip (the same that you downloaded) on device for USB cable on download folder.
Reboot to official recovery (It not work on custom recovery)
Flash for file, search the ozip file and install normally.
It will solve the problem.
* You will not lose the IMEI
* The fingerprint sensor doesn't works. I will try to solve this issue now.
EDIT:
I used a new software to decrypt the ofp
GitHub - bkerler/oppo_decrypt: Oppo .ofp Firmware decrypter and oneplus .ops de-/encrypter
Oppo .ofp Firmware decrypter and oneplus .ops de-/encrypter - GitHub - bkerler/oppo_decrypt: Oppo .ofp Firmware decrypter and oneplus .ops de-/encrypter
github.com
Works very well in Linux, in Windows I don't know.
Open a terminal in directory os unzip the downloaded code
The command used was (in Linux):
./ofp_qc_decrypt.py <your file.ofp> <place to extract/decrypt>
And now I used OTG USB instead SdCard and works too.
OBS:
For fingerprint issue the only way yet is to restore the Persist partition backup generated by PBRP to but I haven't my persistent partition (original) to try, my realme was bricked before that I make it.
I study for a week to recovery my device, and I appreciate each one here what contribuited of a little tool or with your knowledge of the Android system.
I wish what this tutorial help you.
Good luck for all.
"MCT ofp extract tool" is a virus
nirmago said:
"MCT ofp extract tool" is a virus
Click to expand...
Click to collapse
You can search this tool of another site, or using another tool what extract OFP images, feel free to use since what the tool extract the files cited in tutorial. I used this tool and works fine for me.
I used the VM to extract all files bcz I use linux, but you can use VM too and after you can delete the VM.
Isn't it easier to flash those extracted IMG files directly from fastboot, rather than flashing PBRP and working with SD card? Wipe and flashing OZIP can be done thru stock recovery too.
Code:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
lapist said:
Isn't it easier to flash those extracted IMG files directly from fastboot, rather than flashing PBRP and working with SD card? Wipe and flashing OZIP can be done thru stock recovery too.
Code:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Hello man!
Yep it is easier in theory, but doesn't works in practical.
In my case the device lose the stock recovery, I had /boot/recovery not found and the sotck recovery is dependent of super partition to works, if you flash only official recovery will have the error /boot/recovery not found. I did not have system, boot, vendor, nothing anymore in my device. When you have the total softbrick you have 2 things only the bootloader menu (if you unlocked it) and EDL, the EDL in Oppo/realme is complicated why they don't developer any tool to help us in flash for EDL, like Samsung (ODIN) Xioami (XiaomiFlashTool) or OnePlus. And to get worse the ozip and ofp only is used for Oppo/Realme any tool works.
Why not flash the partitions directally with fastboot?
The fastboot when transfering files with USB have some limitations when you work with bigger files 3GB or higher. And many limitations too with partitions, when I talk about open partitions of MB like recovery, boot, and vbmeta ok, the flash done with success, but the partition vendor and system in oppo/realme have the name Super, (\system+\vendor) and fastboot doesn't got write in this partition when your device is in softbrick, then unfortunately the last chance to flash this partition is PBRP this tool use the device like root permissions, I try with SHRP and Orange fox too, but give me errors like mount failed /system_root, and /vendor and SHRP don't flash img files.
The only way what I founded was PBRP flash the img direct to super partition, its solved my problems with don´t flah any zip file with PBRP, the super.img is the key to solve most problems.
I try flash with fastboot, and give me the error "Error: not is possible to format with RAW partitions, check the device terminal." It's happen bcz the fastboot could,t get write in partition system and vendor (or super) bcz the partitions for security are close to fastboot or adb. Was it is all what I discovered in some russian forums. And thanks to developers of PBRP and my efforts I got using my device again.
Why PBRP is good and why I used this tool?
PBRP transform ozip in zip, then he have the capacity of work with ozip very well
PBRP uncrypted my data files
Works with zip and img very easy
Your file explorer is great, better than TWRP, (and remember we don't have TWRP to Realme 7 pro).
Well is it.
I think I managed to explain everything.
Good luck!
I hope I've helped u man.
nirmago said:
"MCT ofp extract tool" is a virus
Click to expand...
Click to collapse
Thanks man. The file really have a virus.
I did according to this guide.
But i have a few file super??
I do this .bat file (
"@Echo off
fastboot flash boot boot.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
"
)
and working recovery and install .ozip
and now i have bootloap to fastboot.. i flash recovery and not working(stock and custom) all time restart to bootloader why???????
p1w3xxx said:
I did according to this guide.
But i have a few file super??
I do this .bat file (
"@Echo off
fastboot flash boot boot.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
"
)
and working recovery and install .ozip
and now i have bootloap to fastboot.. i flash recovery and not working(stock and custom) all time restart to bootloader why???????
Click to expand...
Click to collapse
Hello man!
Something was wrong, bcz after extraction of rom you will have just one super file not all this in your image, how do you make the extraction of rom?
And after extract you have a lot files of 124 files in a folder.
Note that you have a divided super file image, with many sizes, the extraction should join all in only one, see the picture below to see, 124 files and 1 super.img file.
The problem is how you is making the extraction, if you dont use the correct tool you never extract the filer correctly, and in some point you have errors in partitions write. Try to use the tool that I used in tutorial, I search a lot and try many others ways to unbrick and only this tool solved my problem of extract.
This is your first problem.
The second problem is write the partitions, never write partitions with size up 1GB for abd or fastboot, this a limitation of reading and writing.
Ever ever EVER use the TWRP.
And you can use the MCT ofp extract tool, but this files and all that I download have a virus harder to get out the system, this works too. But is very dangerous , use this MCT ofp extract tool if you have another old machine with windows, or a pc that you can format after extraction process, bcz this virus attack the file manager of windows, if you don't have another old pc to try, I don't recommend the MCT ofp extract tool.
The files below was extract with oppo_decrypt using python 3.8 version. I use Linux system, it know what it works in windows too, but don't question me how, I don't know.
Can u see in image? 124 files, and only one super file!
Use the tool what I'd tested in this tutorial using with python. I think what you have a problem with extraction. See well you have two points very importants here:
1 The rom what you is using and the Android version what you system have before brick.
2 The super file, this file have up 8GB and have all system root separate by internal partitions. Why this? Simple, the android have a lot of partitions now, and the super rewrite then on your real locations, if you have a lot of super is wrong. I will post an image to illustrate what you see after extraction, and size of super file.
Please review your extraction. and don't use batch methods, make all changes in realme directly in TWRP, I recommend the PBRP to modify these files.
See the images what I posted now in tutorial. Remember after extract you will have 124 files in a folder with 11.8Gb of files. And a super file sizing 8Gb.
The fact that you have a loop is for your super.img the file was write incorrect or incomplete, and the system don't can charge to another partition. An analogy to you undertstanding it is:
"You try to turn on a car but the car doest have a battery doesnt matter how many times you try turn the key the car never will pass to turn on stats."
The first thing to do to fix the bootloop is write the first partition of android, the android have 2 essencial first partitions, vbmeta and recovery, and no they don't stays in same partitions, the vbmeta controls the part of turn on, and recovery controls recovery.
Then I think that your device stay in a infinite recovery/system bootloop, whats is this? if you enter in fastboot the smartphone restarts automacally, and the system is same.
Well when you writed the files you writed the wrong files this is the cause of boobtloop. Another analogy is:
"You try to turn on the car with a wrong key"
To solve it, first and very quick enter in fastboot, I don't remember if vol+ + power or vol- + power, and insert the correct vbmeta image, the device will reboot again, its normal, and after put the recovery, orangefox or PBRP to stop the fastboot bootloop, and after make the process again but now correctally, with the right files and step by step with calm, and attention. Make it quick bcz the smartphone is in infinite bootloop, then you have some seconds to do it.
Sorry for redundancy in reply but is very important to you understand all process for no have errors.
xxx8086 said:
Hello man!
Something was wrong, bcz after extraction of rom you will have just one super file not all this in your image, how do you make the extraction of rom?
And after extract you have a lot files of 124 files in a folder.
Note that you have a divided super file image, with many sizes, the extraction should join all in only one, see the picture below to see, 124 files and 1 super.img file.
The problem is how you is making the extraction, if you dont use the correct tool you never extract the filer correctly, and in some point you have errors in partitions write. Try to use the tool that I used in tutorial, I search a lot and try many others ways to unbrick and only this tool solved my problem of extract.
This is your first problem.
The second problem is write the partitions, never write partitions with size up 1GB for abd or fastboot, this a limitation of reading and writing.
Ever ever EVER use the TWRP.
And you can use the MCT ofp extract tool, but this files and all that I download have a virus harder to get out the system, this works too. But is very dangerous , use this MCT ofp extract tool if you have another old machine with windows, or a pc that you can format after extraction process, bcz this virus attack the file manager of windows, if you don't have another old pc to try, I don't recommend the MCT ofp extract tool.
The files below was extract with oppo_decrypt using python 3.8 version. I use Linux system, it know what it works in windows too, but don't question me how, I don't know.
View attachment 5473915
Can u see in image? 124 files, and only one super file!
Use the tool what I'd tested in this tutorial using with python. I think what you have a problem with extraction. See well you have two points very importants here:
1 The rom what you is using and the Android version what you system have before brick.
2 The super file, this file have up 8GB and have all system root separate by internal partitions. Why this? Simple, the android have a lot of partitions now, and the super rewrite then on your real locations, if you have a lot of super is wrong. I will post an image to illustrate what you see after extraction, and size of super file.
Please review your extraction. and don't use batch methods, make all changes in realme directly in TWRP, I recommend the PBRP to modify these files.
See the images what I posted now in tutorial. Remember after extract you will have 124 files in a folder with 11.8Gb of files. And a super file sizing 8Gb.
The fact that you have a loop is for your super.img the file was write incorrect or incomplete, and the system don't can charge to another partition. An analogy to you undertstanding it is:
"You try to turn on a car but the car doest have a battery doesnt matter how many times you try turn the key the car never will pass to turn on stats."
The first thing to do to fix the bootloop is write the first partition of android, the android have 2 essencial first partitions, vbmeta and recovery, and no they don't stays in same partitions, the vbmeta controls the part of turn on, and recovery controls recovery.
Then I think that your device stay in a infinite recovery/system bootloop, whats is this? if you enter in fastboot the smartphone restarts automacally, and the system is same.
Well when you writed the files you writed the wrong files this is the cause of boobtloop. Another analogy is:
"You try to turn on the car with a wrong key"
To solve it, first and very quick enter in fastboot, I don't remember if vol+ + power or vol- + power, and insert the correct vbmeta image, the device will reboot again, its normal, and after put the recovery, orangefox or PBRP to stop the fastboot bootloop, and after make the process again but now correctally, with the right files and step by step with calm, and attention. Make it quick bcz the smartphone is in infinite bootloop, then you have some seconds to do it.
Sorry for redundancy in reply but is very important to you understand all process for no have errors.
Click to expand...
Click to collapse
Hello,
i do not understand.. i can't upload recovery.. in cmd everything is okey.. when i want open recovery, phone do restart bootloader.. now when i want open recovery, bad file flash or i don't know what, my phone "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
My question: how should i upload recovery and run it??
p1w3xxx said:
Hello,
i do not understand.. i can't upload recovery.. in cmd everything is okey.. when i want open recovery, phone do restart bootloader.. now when i want open recovery, bad file flash or i don't know what, my phone "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
My question: how should i upload recovery and run it??
Click to expand...
Click to collapse
Press vol- + power at the device turn on in fastboot after flash a good vbmeta.img, and a boot image, I recommend search it in the original rom, and after flash a recovery image (orangefox or PBRP).
But be quick before the device reboot.
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
xxx8086 said:
Press vol- + power at the device turn on in fastboot after flash a good vbmeta.img, and a boot image, I recommend search it in the original rom, and after flash a recovery image (orangefox or PBRP).
But be quick before the device reboot.
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Can u upload for me this file ? Maybe my computer has problem with this.. idk..
p1w3xxx said:
Can u upload for me this file ? Maybe my computer has problem with this.. idk..
Click to expand...
Click to collapse
Rename PBRP to recovery before to flash.
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Link to download PBRP if necessary.
[RECOVERY][UNOFFICIAL][RMX2170][v3.0.0] Pitch Black Recovery [10/12/20]
/* *Disclaimer * * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
Link to OrangeFox
Mayur - marshmello projects - Browse /RMX2170/OrangeFox at SourceForge.net
sourceforge.net
after use this command:
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot recovery
my phone (attach file)
second attach file bootloader.
what i do wrong??
EDIT1:
install fox recovery and working recovery..
but when i want install custom .zip i see error(attach file 3)
You have an error of partitions!
Error 1 in zip describes a permission error and this error is bcz orangefox, try pbrp to try solve it. Some Orange recovery have an error about permissions in Android.
But other recovery not working..
Realme have a good hardware but bad softwares. All it is easilly solved if they had a tool like miflash or samaung Odin.
But...How they don't have... Let's go.
Are you tried write PBRP directally for Orangefox? Inside OrangeFox have a option to write files and partitions, but I don't remember where is it.
Note - You can't install any custom rom before you have a system working with all partitions defined and all running fine. Bcz the custom roms don't create a new partitions, only rewrite over the same system partitions. In your case you have't any system partitions.
And you
yes, tried a few recovery update for OrangeFox and nothing..
I can install a few .img, which files i need install from shapeshiftOS.zip to working my devices???
xxx8086 said:
Hello man!
Something was wrong, bcz after extraction of rom you will have just one super file not all this in your image, how do you make the extraction of rom?
And after extract you have a lot files of 124 files in a folder.
Note that you have a divided super file image, with many sizes, the extraction should join all in only one, see the picture below to see, 124 files and 1 super.img file.
The problem is how you is making the extraction, if you dont use the correct tool you never extract the filer correctly, and in some point you have errors in partitions write. Try to use the tool that I used in tutorial, I search a lot and try many others ways to unbrick and only this tool solved my problem of extract.
This is your first problem.
The second problem is write the partitions, never write partitions with size up 1GB for abd or fastboot, this a limitation of reading and writing.
Ever ever EVER use the TWRP.
And you can use the MCT ofp extract tool, but this files and all that I download have a virus harder to get out the system, this works too. But is very dangerous , use this MCT ofp extract tool if you have another old machine with windows, or a pc that you can format after extraction process, bcz this virus attack the file manager of windows, if you don't have another old pc to try, I don't recommend the MCT ofp extract tool.
The files below was extract with oppo_decrypt using python 3.8 version. I use Linux system, it know what it works in windows too, but don't question me how, I don't know.
View attachment 5473915
Can u see in image? 124 files, and only one super file!
Use the tool what I'd tested in this tutorial using with python. I think what you have a problem with extraction. See well you have two points very importants here:
1 The rom what you is using and the Android version what you system have before brick.
2 The super file, this file have up 8GB and have all system root separate by internal partitions. Why this? Simple, the android have a lot of partitions now, and the super rewrite then on your real locations, if you have a lot of super is wrong. I will post an image to illustrate what you see after extraction, and size of super file.
Please review your extraction. and don't use batch methods, make all changes in realme directly in TWRP, I recommend the PBRP to modify these files.
See the images what I posted now in tutorial. Remember after extract you will have 124 files in a folder with 11.8Gb of files. And a super file sizing 8Gb.
The fact that you have a loop is for your super.img the file was write incorrect or incomplete, and the system don't can charge to another partition. An analogy to you undertstanding it is:
"You try to turn on a car but the car doest have a battery doesnt matter how many times you try turn the key the car never will pass to turn on stats."
The first thing to do to fix the bootloop is write the first partition of android, the android have 2 essencial first partitions, vbmeta and recovery, and no they don't stays in same partitions, the vbmeta controls the part of turn on, and recovery controls recovery.
Then I think that your device stay in a infinite recovery/system bootloop, whats is this? if you enter in fastboot the smartphone restarts automacally, and the system is same.
Well when you writed the files you writed the wrong files this is the cause of boobtloop. Another analogy is:
"You try to turn on the car with a wrong key"
To solve it, first and very quick enter in fastboot, I don't remember if vol+ + power or vol- + power, and insert the correct vbmeta image, the device will reboot again, its normal, and after put the recovery, orangefox or PBRP to stop the fastboot bootloop, and after make the process again but now correctally, with the right files and step by step with calm, and attention. Make it quick bcz the smartphone is in infinite bootloop, then you have some seconds to do it.
Sorry for redundancy in reply but is very important to you understand all process for no have errors.
Click to expand...
Click to collapse
hi, i repaired my device, but now i have other problem
don't working any bank application.. need latest version rom..
phone don't look new update.. i try change vpn (nord vpn) inida, deutchland NOTHING
i have this rom: RMX2170PU_11.A.41
i will try a few ofp file with android 11 but every have a few super.img... : attach 1
i have files: attach 2 and 3
only in rom ...A37... one files super.img but not working any bank application
Thanks man it's really helpful for me.
Heya, I wasn't sure whether to put this under Theming, it is half a question and half a list of my discoveries
I'll be putting em here in hopes of better code nerds figuring out the language this thing speaks for custom boot logos
Tl;Dr is I'm trying to get custom boot logos to work on my F4, everything I could gather is below.
Compared to the normal process of there existing a file like splash.img or boot.img as you would find in a F2 Pro or F3, the F4 has neither
To be more specific, there exists a device partition in /dev/block/bootdevice/by-name/splash, which is a few symlinks to the actual device /dev/block/sda20
However, trying to dd sda20 results a 34MB file of naught but zeroes, viewed in a hex editor it is completely empty.
My guess is this stems from the Virtual A/B partitioning and whatever new boot scheme the peeps what enginerded this thing came up with, making /dev/block/ obsolete.
Side note, I did attempt flashing a logo.img made with the K30 Util (download below) with:
Code:
fastboot flash splash logo.img
Also tried flashing a splash.img made with a barebones Splash util (again, download below), ran:
Code:
fastboot flash splash splash.img
Both cases succeeded in flashing but the logo didn't change, completely ignored it and booted normally. Didn't even brick the device. The nerve.
Half question, half Theme, can anyone help me figure this out?
Links:
K30 Logo Utility (GDrive, 7z, credits to Pzqqt and Gokul NC)
Splash Logo Maker (Generic)
chihirofujo said:
Heya, I wasn't sure whether to put this under Theming, it is half a question and half a list of my discoveries
I'll be putting em here in hopes of better code nerds figuring out the language this thing speaks for custom boot logos
Click to expand...
Click to collapse
I also tried on my Xiaomi 12 pro without success while on the F2 pro no problem.
This is probably due to partitions A / b but especially that the partitions at the level of this sector is write protected.
.\fastboot flash logo_ab logo.img not working.
helo im chiense,
i belicve this is cause by xiaomi protectoing the splash image partitont on a/b phone z
hope this help!!
What about flashing from fastbootD? Will it works?
Hello guys, does any of you have a stock boot splash/logo mod without unlocked logo/text, which is working for poco f4 ? (I need this to hide my bootloader unlock status from bootsplash screen, so that in case of device brick, service center guys will not know its unlocked by just looking at it )
sachin karinki said:
Hello guys, does any of you have a stock boot splash/logo mod without unlocked logo/text, which is working for poco f4 ? (I need this to hide my bootloader unlock status from bootsplash screen, so that in case of device brick, service center guys will not know its unlocked by just looking at it )
Click to expand...
Click to collapse
Unlocking the bootloader does not void warranty.