Database Develop

Stuck without an update

Hello,
Lately I've altered my system a bit and had to restore it to it's previous setup using pre-rooted boot.img and flashing back again "June08_NB1_v4.88B" OTA update. I've been on June update and this zip clearly for some unknown reason rolled me back into May secruity update.
Now whenever I try to update my device with auto updates back on into June or July it gives me this error message :
{
"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"
}
Now I can't automatically get updates, but my attempts to use 4.88C which is July revision of security updates the recovery gives me a message that it's designed for 4.88B.
Now the question is - has somebody encountered a similar issue ? If so what can be done in this situation to get back automatic updates ?

Got it to work by wiping clean system, boot_a and boot_b.
Reflashed the stock paritions in their places from 4.88B with May security update.
My suspect in crime was busybox update that was installed system-wide directly into system & boot partitions which caused OTA mismatch and refusal of installation.

nice work done there.. hope it will help other people who are stuck too..
Sent from my Nokia 8 using XDA Labs

Hi,
Can you explain your method. I'm actually on 4.88B and I can't get no more security patch (still 1st may 2018).
Do you flash via fastboot (can you tell us the command lines)
Excuse my english

I've downlaoded both OTA and paritions zip. Flashed boot_a and boot_b using boot.img <fastboot flash boot_a boot.img; fastboot flash boot_b boot.img>
Then I did relock my OEM which resulted in a loopboot due to modified partitions, that's how I figured out to reflash OTA with update from SDCard using android stock recovery.

no unlocked bootloader, no flash.....
I hope an OTA in Android O with version higher than 4.88B....

Bricked Huawei P smart 2018 FIG-LX1 stuck in ERROR MODE

EDIT: I could fix this, if you have a device that works with HuRUpdater just download an update.zip, put that and the HuRUpdater zip in a new folder and it updates the recovery through TWRP so that's how I fixed it.
So I'm stuck in ERROR MODE. The only mode that works for me is Fastboot. I tried to reinstall recovery_ramdisk, system, cust and userdata but still in the same error. Before the brick EMUI 9.1 was installed. I've tried to install LineageOS 16 on my phone with TWRP, but I got error 7. First I've restored the nanddroid backup and I went stuck at a bootloop. I've entered eRecovery and downloaded the lastest version available on server and got this error. Any solutions for it? And the bootloader is unlocked, same with FRP. The error that shows in the screen
{
"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"
}
is Func. NO: 11 (recovery image) and Error NO: 2 (load failed). Would be appreciated if someone answers.
Here is how Fastboot looks like...

I've had a similar situation which I got out of using advice from this forum. Basically, I erased data from fastboot, flashed the stock 9.1 recovery (which I found a link for in one of the P Smart ROM threads) and lineage boot.img.
I MAY also have powered on with BOTH volume keys pressed.
You do have fastboot access, so I'd guess you will eventually be able to recover via the stock recovery.

Another_Alchemist said:
I've had a similar situation which I got out of using advice from this forum. Basically, I erased data from fastboot, flashed the stock 9.1 recovery (which I found a link for in one of the P Smart ROM threads) and lineage boot.img.
I MAY also have powered on with BOTH volume keys pressed.
You do have fastboot access, so I'd guess you will eventually be able to recover via the stock recovery.
Click to expand...
Click to collapse
Thanks for the help but forget this, I could fix it, I'm gonna modify the thread to inform that I could solve it. I finally could access twrp via the 3 button update method and used HuRUpdater to update the recovery and could fix the phone with an EMUI 8 rom and recovery that I flashed with HuRUpdater. Also, I could install LineageOS without ERROR 7 by modifying a text file in the ROM zip. Thanks anyway.

LucastheBowser said:
Thanks for the help but forget this, I could fix it, I'm gonna modify the thread to inform that I could solve it. I finally could access twrp via the 3 button update method and used HuRUpdater to update the recovery and could fix the phone with an EMUI 8 rom and recovery that I flashed with HuRUpdater. Also, I could install LineageOS without ERROR 7 by modifying a text file in the ROM zip. Thanks anyway.
Click to expand...
Click to collapse
Hello! It seems Im having a same problem, since this device is somewhat discontinued by huawei, I cannot update it to any version, and cannot downgrade it either, using the "classic" sdcard method. Could you tell me how you used HuRupdater to flash the rom on yours?

The Solution for me->
Full package->
Software.rar
drive.google.com
Put your device on Testpoint mode:
Disconect the batery, join the point to gnd and conect usb cable on your pc.
and ..

and later you can update by SD

After update security pixel 4xl " your device corrupt"

{
"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"
}

Well, without more information about the actual error message... my suggestion would be to flash a full image from Google without the wipe command flag. (You remove the "-w" from the flash-all.bat)
You can try using the browser based flash tool if downloading platform tools/ADB is too much for you. It's supposedly easier, but I've never used it before. It also might wipe your device by default, so be careful?

MBenzKH said:
Help!
Click to expand...
Click to collapse
Being bootloader locked, about the only thing you can do is flash a FULL OTA IMAGE available from Google's website and flash it from recovery using ADB. This procedure has also been called a "rescue ota". You cannot flash a full image via fastboot (because you are locked) but you can flash the OTA from recovery. There are instructions on Google's download page. Just pick the newest OTA image available. The most important thing is to get adb/fastboot set up correctly on your PC. Always easier to learn when your phone is working properly, but still not that difficult to accomplish and verify proper installation. Start with the very latest (February 2021) adb/fastboot binaries. Drop those files (and the image) into a folder and add that folder to your path statement. ADB only works in recovery NOT in fastboot mode like your screenshot. If you have questions or need more info, PM me.

v12xke said:
Being bootloader locked, about the only thing you can do is flash a FULL OTA IMAGE available from Google's website and flash it from recovery using ADB. This procedure has also been called a "rescue ota". You cannot flash a full image via fastboot (because you are locked) but you can flash the OTA from recovery. There are instructions on Google's download page. Just pick the newest OTA image available. The most important thing is to get adb/fastboot set up correctly on your PC. Always easier to learn when your phone is working properly, but still not that difficult to accomplish and verify proper installation. Start with the very latest (February 2021) adb/fastboot binaries. Drop those files (and the image) into a folder and add that folder to your path statement. ADB only works in recovery NOT in fastboot mode like your screenshot. If you have questions or need more info, PM me.
Click to expand...
Click to collapse
I've not had a locked boot loader for longer than 7 days in the past decade, so my experience is poor... but I always thought that the locked bootloader would deny usage of foriegn images like a Magisk patched boot.img or something else. It's surprising to me that you would not be able to flash a full Google image directly with Fastboot. Am I wrong?

jljtgr said:
I've not had a locked boot loader for longer than 7 days in the past decade, so my experience is poor... but I always thought that the locked bootloader would deny usage of foriegn images like a Magisk patched boot.img or something else. It's surprising to me that you would not be able to flash a full Google image directly with Fastboot. Am I wrong?
Click to expand...
Click to collapse
From the screenshot provided, OP's bootloader is locked, so he cannot fastboot flash ANYTHING. Within the stock recovery there is an option to flash a full OTA image via ADB from a laptop or PC. A recovery OTA is the only way forward in this case, and is dependent on whether he has a working recovery. I've seen this method save many bootloader locked phones. Hopefully OP will come back and let us know he was successful.

Question How to update or reflash stock samsung firmware if you are rooted?

I have rooted S21 ultra Exnos it has TWRP and decrypted what i want to ask is
If there is new firmware released which i want to update it then what is the procedure so that i can have my settings , root. and internal storage date? even TWRP
as device is decrypted if i flash the stock samsung firmware via ODIN then it will encrypt storage again right? which will format my internal storage as that is main thing... which i dont want and will overwrite the stock recovery also
please let me know options in comments

First, search for the ROM that you'd like and find out what suites you best yourself, that way you're more aware of the risks and what you actually need.
Second, flashing any ROM on decrypted device doesn't encrypt it again as long as you flash the decryption zip again like dm-verity, and flashing ROM with ODIN doesn't replace the recovery. You need to flash recovery through "AP" to do that.
Goodluck.

XDHx86 said:
First, search for the ROM that you'd like and find out what suites you best yourself, that way you're more aware of the risks and what you actually need.
Second, flashing any ROM on decrypted device doesn't encrypt it again as long as you flash the decryption zip again like dm-verity, and flashing ROM with ODIN doesn't replace the recovery. You need to flash recovery through "AP" to do that.
Goodluck.
Click to expand...
Click to collapse
i was talking about G998BXXU3AUF6 Samsung stock firmware which has 5 files total in ZIP but we need to flash 4 including AP
and i was not aware of that dm-verity zip will work in Samsung devices too as i decrypted it by the method which was mentioned in TWRP by command multi disabler
{
"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"
}

nitinvaid said:
i was talking about G998BXXU3AUF6 Samsung stock firmware which has 5 files total in ZIP but we need to flash 4 including AP
and i was not aware of that dm-verity zip will work in Samsung devices too as i decrypted it by the method which was mentioned in TWRP by command multi disabler
View attachment 5353701
Click to expand...
Click to collapse
If you mean stock ROM you can get yours from sammobile it has whole archive of ROMs.
DM-Varity was just an example, you can use whatever works for you.
Also you can always just flash TWRP again. No biggie.

How To Guide Guide to Flash Miui_VILIGlobal_V13.0.1.0.SKDMIXM_e7e8f0ef90_12 and use Magisk

Hello All,
Quick and dirty guide.
Warning!
I'm not responsible for any damage to you, to your device or to your data. Do this at your OWN RISK! If you don't know what you are doing, STOP now!
Steps to flash the ROM using TWRP:
Be on Android 11 (MIUI 12.5) and flash TWRP. There is a guide here on how to do it, so i'm not posting that.
Obviously, you'll need unlocked bootloader so if it's not unlocked, your case is lost
Download the ROM in the title from here and copy it to your phone
Reboot to TWRP
If you want, i guess you can wipe data - i haven't done this
Flash the ROM like you would any other (install and select the zip you copied over from the above link)
At the end, it'll give you mounting error but it's all good, reboot
Wait for the ROM to settle if you wish - you can stop here
For Magisk, follow the below steps
Enable developer settings and USB debugging
Install the Magisk Manager app (latest version 24.1 at the time of writing this little guide)
Turn off the phone and boot it into fastboot mode
Start the fastboot app of your choice from your pc and connect your phone via USB (I'm using Minimal ADB and Fastboot, you can find it on XDA)
issue the following commands in the same order:
Code:
fastboot devices
if you don't get as a response a few digits of your device ID with the fastboot text next to it, you'll doing something wrong (driver might be or you are not in fastboot mode)
Code:
fastboot flash boot_a patched_boot.img
if the command completes you'll get a finished message
Code:
fastboot flash boot_b patched_boot.img
patched_boot.img is the full path of the patched boot.img file
Code:
fastboot reboot
wait for the device to boot.
Patched boot.img is attached but if you wish, you can extract it from the rom yourself using payload dumper and patch it on your phone with Magisk. The attached boot.img is patched with Magisk 24.1, this is what you'll need as well - this is the current version. You need to unzip the attached file of course!
Enjoy.

{
"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 flashed by TWRP and reset to the factory. So far there is no fastboot image, only recovery one, and normal way it is not possible to flash it as it is only for Mi Pilot people.

Pichulec said:
Just flashed by TWRP and reset to the factory. So far there is no fastboot image, only recovery one, and normal way it is not possible to flash it as it is only for Mi Pilot people.
Click to expand...
Click to collapse
what do you mean with "no fastboot image"?

There are two types of images - recovery and fastboot.

Hello, im trying your guide but my phone stuck on fastboot mode and when im try to enter twrp, it stuck on frozen screen i cant swipe to unlock twrp....any idea?(

Yuditkiichi said:
Hello, im trying your guide but my phone stuck on fastboot mode and when im try to enter twrp, it stuck on frozen screen i cant swipe to unlock twrp....any idea?(
Click to expand...
Click to collapse
Hi, if TWRP worked before, it should as well now.

donjamal said:
Hi, if TWRP worked before, it should as well now.
Click to expand...
Click to collapse
Any idea how to solved my twrp problem? Or should i reflash it with pc?

Yuditkiichi said:
Any idea how to solved my twrp problem? Or should i reflash it with pc?
Click to expand...
Click to collapse
I would probably relfash twrp as long as I'm still on 12.5.

Yesterday received OTA update for my 11t pro. I'm not in Pilot Programm..

Yuditkiichi said:
Any idea how to solved my twrp problem? Or should i reflash it with pc?
Click to expand...
Click to collapse
for now twrp not working for a12.
wait for update

All can download rom here https://xiaomifirmwareupdater.com/miui/vili/stable beta/V13.0.1.0.SKDMIXM/
and use updater to update it.. that dont need any mi pilot.. i just installing it.. yeeah!