{
"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've an infinix note 8i with following build number :
X683-H694EFGHIJUW-Q-OP-210831V351
I've unlocked the bootloader. But I can't find the firmware that matches my phones build number. The latest firmware that I found was :
Infinix_Note_8i_X683_MT6768_V332_210305
So obviously the build numbers are not the same. So I need solutions on what to do? Should I use this unmatched build version firmware to root my device? Or maybe I can extract my stock firmware somehow? And also another thing, some were saying I needed to flash empty vbmeta file before flashing patched boot image. So where would I get the empty vbmeta file?
Thanks In Advance.
With regards to vbmeta.img:
It doesn't matter what kind of vbmeta is used, because fastboot only changes 2 bytes on a specfic address in it which are parsed by the botloader. But the vmeta must have at least a size of 4KB.
Have attached a blank vbmeta.
jwoegerbauer said:
With regards to vbmeta.img:
It doesn't matter what kind of vbmeta is used, because fastboot only changes 2 bytes on a specfic address in it which are parsed by the botloader. But the vmeta must have at least a size of 4KB.
Have attached a blank vbmeta.
Click to expand...
Click to collapse
Thanks A Lot, Just finished rooting my device finally, though I experienced one bootloop but fixed it via SP Flash Tool. Guess I would post a detailed thread of how I did it cause there isn't much help on the internet about this model.
sharifrafid said:
Thanks A Lot, Just finished rooting my device finally, though I experienced one bootloop but fixed it via SP Flash Tool. Guess I would post a detailed thread of how I did it cause there isn't much help on the internet about this model.
Click to expand...
Click to collapse
Did you manage to root it with this build number or did you downgrade?
anthonymatar1 said:
Did you manage to root it with this build number or did you downgrade?
Click to expand...
Click to collapse
Well, first I tried with this build number and root was successful but then my Bluetooth and Wifi was not working at all. So then I had to downgrade to v332 and then root again. Now things are running perfectly.
sharifrafid said:
Well, first I tried with this build number and root was successful but then my Bluetooth and Wifi was not working at all. So then I had to downgrade to v332 and then root again. Now things are running perfectly.
Click to expand...
Click to collapse
Did you try to update your device after rooting it?
@anthonymatar1 Nope, but I think there's a high chance that updating your device will result in a brick or something. I wouldn't suggest it.
INFINIX NOTE 8i UNOFFICIAL TWRP X683
DOWNLOAD
Just Follow the Guide
mastersenpai05 said:
INFINIX NOTE 8i UNOFFICIAL TWRP X683
DOWNLOAD
Just Follow the Guide
Click to expand...
Click to collapse
Will it work for this build number X683-H694EFGHIJUW-Q-OP-220318V387
Related
Here is the stock boot image of the latest and the last update for Nokia 8 extracted from stock ROM. It can be downloaded from attachments (Boot_5_16A.rar). Simply extract the downloaded file to have the image. It should be about 52 MB in size. It is perfectly compatible with the latest TWRP and easily rootable by magisk. In the case of bootloop caused by flashing improper image to boot partition (like not compatible recovery image) flash it to the corrupted slot.
Also full OTA (for build number 00WW_5_150) is provided here. This is a maintenance release (MR) update and is flashable by stock recovery, won't factory reset your phone, and is usable for all variants of Nokia 8. I have been using it for a week or so. No problem is seen, though it's hard to point out any significant improvement.
{
"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"
}
Arashone said:
Here is the stock boot image of the latest and the last update for Nokia 8 extracted from stock ROM. It can be downloaded from attachments (Boot_5_16A.rar). Simply extract the downloaded file to have the image. It should be about 52 MB in size. It is perfectly compatible with the latest TWRP and easily rootable by magisk. In the case of bootloop caused by flashing improper image to boot partition (like not compatible recovery image) flash it to the corrupted slot.
Also full OTA (for build number 00WW_5_150) is provided here. This is a maintenance release (MR) update and is flashable by stock recovery, won't factory reset your phone, and is usable for all variants of Nokia 8. I have been using it for a week or so. No problem is seen, though it's hard to point out any significant improvement.
View attachment 5201721
Click to expand...
Click to collapse
Thank you so much.
It works very well
Hi @Arashone,
Could you compare against 5.15G to see what changed?
Cheers
madb1lly said:
Hi @Arashone,
Could you compare against 5.15G to see what changed?
Cheers
Click to expand...
Click to collapse
Actually, I see no change. Nokia didn't publish changelog or something like that either. So as of now, just using!
Arashone said:
Actually, I see no change. Nokia didn't publish changelog or something like that either. So as of now, just using!
Click to expand...
Click to collapse
Ah, I thought you had compared the files and checksums between versions for some reason. Can someone do that? Or if someone can tell me where the full images are for these two versions and how to unzip them then I'll so it.
Cheers
While trying to flash Lineage OS I'm encountering a ton of hurdles. The current guide I'm on: https://www.getdroidtips.com/resurrection-remix-google-pixel-4a/
Says I need to install some Resurrection Remix image? I think I may be missing something. The alternative is GrapheneOS which appears FAR FAR FAR FAR FAR simpler to flash onto a device. But I don't want my first step to be such a big one where I lose so much.
How to Install TWRP Recovery on Google Pixel 4a and Root it
On this page, we will guide you to install the TWRP Recovery on Google Pixel 4a (sunfish). This guide contains both the written instruct
www.getdroidtips.com
I'm following those instructions.
I am currently;
Code:
fastboot flash recovery twrpname.img
I get an error. I wish I had written it down but it was essentially command failed.
For "twrpname.img" I substituted "twrp201017-test5.img" which is the twrp image I was pointed to elsewhere.
Help would be greatly appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is what I see
... Now when trying to flash grapheneOS I get that my android tools are too old. This is amazing.
anticlutch said:
... Now when trying to flash grapheneOS I get that my android tools are too old. This is amazing.
Click to expand...
Click to collapse
Are you on Android 11 stock? TWRP will only work on a phone with Android 10. So you will have to downgrade before flashing TWRP.
Probably easier to check out the rom section in the Pixel 4a forum than to install TWRp.
anticlutch said:
View attachment 5252207
this is what I see
Click to expand...
Click to collapse
I see a typo in that command, FYI. I don't know if that fixes your problem or not but it should probably be recovery, not recoery.
Did you download SDK Platform-Tools from here? https://developer.android.com/studio/releases/platform-tools
When I downloaded, it was platform-tools_r31.0.1-windows.zip.
This guide might be helpful if you really want TWRP (and Android 10, not Android 11): https://forum.xda-developers.com/t/guide-unlocking-downgrading-to-a10-twrp-root.4233275/
If you just want Lineage 18 then maybe follow this one: https://forum.xda-developers.com/t/...-patch-for-pixel-4a-sunfish-20210308.4208931/
I don't think TWRP is really necessary.
They have same code name and almost same specs. I couldn't find any 12.5 fastboot rom for redmi 9a.
As there is no android 11 supported twrp, I can't flash magisk.
I can't copy the boot .img from the fastboot rom too.
Any ideas?
Flahsing magisk using twrp is the WORST way for flashing magisk.
Use fastboot to flash magisk
NO，you CANT!(I TRIED THAT and bricked it)(can be rescued with Emergency Download Mode)
I have the same device as yours. It's needed to PATCH boot with magisk on the device
I have to tell you that DONT WONDER if TWRP OR IMGs from the redmi 9A to work on this device，since the employee on official Chinese forum said they are INCOMPATIBLE.
{
"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"
}
Just download the latest rom in the system update and you'll find it in downloads folder in your internal storage.
then extract it and find vbmeta.img and boot.img
copy them to somewhere you can find and use magisk app to patch the boot.img.
now copy the 2 imgs to computer
connect and reboot to fastboot,flash boot.img AND VBMETA.img with the option of --disable-verity --disable-verification.
NOW enjoy.
Some people is saying Redmi9A and Redmi10A can share their ROMs.
But, they can NOT.
Everybody should avoid flashing the wrong ROM to your devices.
If you have a Redmi9A, flash DANDELION rom only !!!!
If you have a Redmi10A, flash DANDELION_C3L2 rom only !!!!
If you mix them, you will have catastrophic losses as the FULL USERDATA !!!!
KEEP ATTENTION AND USE YOUR BRAIN !
VD171 said:
Some people is saying Redmi9A and Redmi10A can share their ROMs.
But, they can NOT.
Everybody should avoid flashing the wrong ROM to your devices.
If you have a Redmi9A, flash DANDELION rom only !!!!
If you have a Redmi10A, flash DANDELION_C3L2 rom only !!!!
If you mix them, you will have catastrophic losses as the FULL USERDATA !!!!
KEEP ATTENTION AND USE YOUR BRAIN !
Click to expand...
Click to collapse
good warning since i did tried that lol
sd369888 said:
good warning since i did tried that lol
Click to expand...
Click to collapse
I just tried that recently, too...
Sad.
Op8 i think its was T or V
But after try to unlock bootloader its bricked and now not taking any flash file
I tried many file but the only one error
Trg id error
So i try with smt even with imei loss risk
And the result was as you see in pick
But the worst thing is smt erase all luns
And now my device's is total empty
But just detect 9008
So is there anyway or anyone can fix?
I want to know is there anyway to bypass this id chk? Or direct flash or something?
No worry about payment
{
"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"
}
There should be not be "COM32", or generally any number higher than 6. Check to see if your drivers are defect and try flashing again.
Xryphon said:
There should be not be "COM32", or generally any number higher than 6. Check to see if your drivers are defect and try flashing again.
Click to expand...
Click to collapse
Bro its not issue com Port i flash many time in higher port
Even in this case smt detect and erase all partitions then stuck
Trg id should not be default
Or 0
@Whoareyou
See this bro
Mr Hassan said:
Op8 i think its was T or V
But after try to unlock bootloader its bricked and now not taking any flash file
I tried many file but the only one error
Trg id error
So i try with smt even with imei loss risk
And the result was as you see in pick
But the worst thing is smt erase all luns
And now my device's is total empty
But just detect 9008
So is there anyway or anyone can fix?
I want to know is there anyway to bypass this id chk? Or direct flash or something?
No worry about paymentView attachment 5644461
Click to expand...
Click to collapse
I can help u with it.
Prinçe çharming ap said:
I can help u with it.
Click to expand...
Click to collapse
You can text me on my Telegram to get faster replies.
Hey there,
I have a problem with my A52 (SM-A525F/DS): It doesn't boot anymore, as it is stuck in the Download mode, showing the error message: "Reason recovery: Error verifying vbmeta image: invalid vbmeta header (6)"
Steps that lead to this:
LineageOS is installed. After installation of a software update, Magisk lost its root. So I tried to install an alternative recovery (TWRP) with Odin. Odin said "Pass", but now this error message occurs.
What can I do now to make the phone work again? Install the Stock ROM?
Would you please help me with this issue? Thank you so much.
{
"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"
}
Once again, you need to properly follow all the instructions listed on the thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-for-galaxy-a52-4g-and-a72-4g.4405751/
Thank you and please excuse my stupidity.
@Simon1511, it worked, thanks again.
As this was inititally my problem: Is there a way to use LineageOS with Magisk and install Updates without losing the root access?
fheba said:
@Simon1511, it worked, thanks again.
As this was inititally my problem: Is there a way to use LineageOS with Magisk and install Updates without losing the root access?
Click to expand...
Click to collapse
Not automatically. You would have to reflash magisk every time you install an OTA.
deleted
Simon1511 said:
Not automatically. You would have to reflash magisk every time you install an OTA.
Click to expand...
Click to collapse
Thanks for your answer. I'm curious: Why doesn't it work anymore? It works with older phones like the Samsung A5 2017.
fheba said:
Thanks for your answer. I'm curious: Why doesn't it work anymore? It works with older phones like the Samsung A5 2017.
Click to expand...
Click to collapse
The problem is encryption. On the A5 2017 the Magisk re-install script would run after installing an OTA and would install itself again. But since encryption is enabled by default on newer phones (such as the A52) it doesn't work/behave correctly.
I'm fairly sure though it's an issue with Magisk and not with the ROM.